Sentral 5.8 Administrator s Guide. ClearCube Technology, Inc.

Transcription

1 Sentral 5.8 Administrator s Guide ClearCube Technology, Inc.

2 Copyright 2006, 2007, 2008 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. 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 Sentral, 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: US , US , US , US , US , US , US , US , US , US , US , US , US , US , US , US , US , and US Inquiries regarding patented technology should be directed to ClearCube Corporate Headquarters.

3 Contents Chapter 1: Introduction... 1 Contents of Sentral CD...2 License Requirements...3 Hardware and Software Requirements...3 Minimum System Requirements...3 Software Requirements...4 Supported Operating Systems...5 Supported Thin Clients...6 Sentral Overview...6 Servers...8 Primary Sentral Server...9 Secondary Sentral Server...9 Failover Scenario Workflow...9 Database Server...10 Sentral Console...10 Physical Hosts, Virtual Machine Hosts, and Thin Clients...10 Neoware Thin Clients and ezremote Manager...11 Thin Clients without Operating Systems...11 Virtual Machine Host...11 Starting Quickly...12 Chapter 2: Installing ClearCube Sentral Version Before Installing Sentral...13 Configuring DNS and DHCP for Clients That Do Not Auto-Register...14 Creating a DNS Forward Lookup Zone...14 Creating a DNS Reverse Lookup Zone...16 Configuring DHCP Server...18 Sentral Network Node Name Limitations...20 Enabling Systems for Remote Access...20 Configuring Inbound Network Ports...21 Configuring Network Ports on Windows XP...21 iii

4 Configuring Network Ports on Microsoft Vista...24 Install Your Sentral SQL Database...27 Sentral Installation Overview...27 Installing Sentral Database...29 Automatically Creating the Database during Sentral Installation...29 Manually Creating the Database Schema...29 Installing Sentral Server and Sentral Console...32 Configure Tomcat Authentication for Sentral Server...36 Console-Only Installation...37 Installing Sentral Host Agents on Hosts and Virtual Machines...39 Installing BMC Drivers on A1410 Blades...42 Preparing Thin Clients for Deployment...44 Installing Thin Client Agents...44 Installing on Windows XPe Thin Clients...44 Installing on Neoware Windows XPe Thin Clients...46 Installing on Neoware NeoLinux Thin Clients...47 Configuring DHCP Server for Wyse V10L Thin Clients...48 Adding Predefined Options to DHCP Settings...48 Add Predefined Options to DHCP Scope...50 Running V10L Utility on Sentral FTP Server...52 Configuring Clientless and Web based Host Access...53 Installing the Sentral License...53 Obtaining a Permanent License Key...53 Installing the Permanent License Key...54 Upgrading from Sentral Exporting Configuration Settings...56 Importing Configuration Settings...56 Uninstall Previous Versions of All ClearCube Software...57 Adding I8330 Support to Sentral Installations...57 Upgrading Sentral Console and Server...57 Upgrading Sentral Host Agent...58 Upgrading Sentral Thin clients...59 Integrating Hypervisors and Virtual Machines in Sentral...59 Integrating ESX Hypervisor...59 Enabling ESX Server 3.5 to Communicate with Sentral...60 Enabling ESX Server 3.0.X to Communicate with Sentral...60 Integrating Xen Hypervisor...61 Integrating Virtual Machines in Sentral...62 Integrating ESX and Xen Virtual Machines...62 iv ClearCube Technology, Inc.

5 Integrating Hyper V Virtual Machines...63 Chapter 3: Starting with Sentral Sentral Console Main Menu...66 Hierarchical View...67 Using Hierarchical Node Right-Click Menus...68 Hierarchical View Icons...68 Using Right-Click Menus to Perform Tasks on Nodes in Sentral Screens...70 Menu Buttons...71 Utilization Charts...72 Configuring Dashboard Refresh Time...73 Configuring the Dashboard Scale...73 View Menu...74 Finding Nodes, Groups, and Entities in Sentral...74 Simple Search from Node Listings...75 Advanced Search...76 Sentral Dialog Boxes...78 Table Configuration...78 Choosing Columns to Display in a Table...80 Removing a Column from a Table...80 Changing a Column s Text Label...81 Chapter 4: Configuring the Sentral Console Starting the Sentral Console...84 Configuring the CCT User Account...87 Setting Global Configurations for Sentral...87 Using the Configuration Wizard...88 Using the Configuration Screen...89 Global Configurations and Conditions Requiring a Console and Apache Tomcat Service Restart..95 Limiting Sentral Interaction with Active Directory Groups...95 Configuring SNMP...96 Setting Up Security...97 General Access...98 Advanced Access...98 Function Authorization and Resource Permissions...98 Is Write and Is Execute Resource Permissions...99 Group Authorization Setting up a New Security Group Enabling Login Specifying GUI Access Sentral Administrator s Guide v

6 Creating and Specifying Policies Configuring and Using the CCT User Updating the Console Chapter 5: Managing Sentral Nodes Discovering Sentral Nodes Specifying Subnets to Use For Node Discovery Discover Selected Subnets Discover All Subnets Schedule Discovery Modify Selected Subnet Delete Subnet from Sentral Console Discovering and Adding Users Specifying the User Type to Discover Discovering Users Adding Users to Sentral Management Tasks Managing Chassis Run Chassis Discovery Configuring Chassis Add or Modify an RMC or RMM Delete an RMC or RMM Discover and View Daisy Chains Populate Host Inventory Update Chassis Firmware Update Chassis Group Firmware View Equipment History Configuring Host Connection Limits Managing Hosts Discovering Hosts Discovering Hosts with Dual (V5120) and Quad (V5140) Host Cards Configure a Host View a Host s Health and Status Map a Host to a Thin Client Map a Host to a User Update Client Software for a Host or Host Group Update a Host BIOS or Host Group BIOS Shut Down or Restart a Host View Equipment History for a Host vi ClearCube Technology, Inc.

7 Managing PCoIP Hosts Managing PCoIP Hosts (V5120 Dual Host Cards) Using a Host s AMT Features Set AMT Administrator Deleting Credentials on AMT Host Configure AMT Management AMT Power On AMT Shutdown Host AMT Restart Host AMT Console Redirect Advanced PCoIP Configuration Managing C/Ports Modify a C/Port Delete a C/Port View Equipment History for a C/Port Managing Thin Clients Identifying Thin Clients without Operating Systems in Sentral Discovering Thin Clients Discovering I9420 and I9440 I/Ports Configuring XPe Thin Clients Disabling Mass Storage Devices on XPe Thin Clients Configuring V10LThin Clients View a Thin Client s Health and Status Map a Thin Client to a Host Map a Thin Client to a Virtual Machine Update Thin Client Agent for a Thin Client or a Thin Client Group View Thin Client Equipment History Preserving I94xx Connection Mode During Discovery Managing Virtual Machines Run VM Discovery Adding Hypervisor Information to the Sentral Database Registering ESX VMs in the Sentral Database Powering on a VM Enabling VMs to Automatically Start and Resume Finding All Non-Running VMs on a Host Configure a Virtual Machine Understanding VM Health and Status Information Map a Virtual Machine to a Thin Client Map a Virtual Machine to a User Sentral Administrator s Guide vii

8 Update Client Software (Host Agent) for a Virtual Machine or a Virtual Machine Group..168 Shut Down or Restart a VM View Equipment History for a VM Managing Users Discover Users in the Sentral Environment Adding an Asset Tag to a User Configuring Sentral for User Based Mapping Configuring Sentral for Device Based Mapping Create a Mapping for a User Adding Local and Domain Security Groups to Sentral User Groups Managing Views Add a View Modify a View Delete a View Health & Status Tasks Health & Status Chassis View Health and Status of a Selected Chassis Update a Chassis Firmware View Equipment History for a Chassis View Alerts for a Chassis Health & Status Thin Clients View Health & Status of a Selected Thin Client View Equipment History for a Thin Client Health & Status Hosts View Health and Status of a Selected Host View Equipment History for a Host View Alerts for a Host Health & Status Virtual Machines View Health & Status of a Selected VM View Equipment History for a VM View Alerts for a VM Health & Status Alerts View Alerts Configure Alerts View Deployed Alerts Reports Tasks Reports Inventory Reports Alerts View Logging viii ClearCube Technology, Inc.

9 View Deployed Alerts Configure Alerts Inventory Report Clear All Alerts Clear Selected Alerts Scheduler Report Reports Custom Reports Reports Equipment History Export Equipment History Report Delete Equipment History Reports Device Accessibility Chapter 6: Using Intel Active Management Technology Provisioning AMT on Hosts Enable AMT on the Host Specifying Host Name in Sentral Specifying the AMT Mode Using AMT in Your Sentral Environment Discovering AMT Hosts Viewing Discovered AMT Hosts Performing AMT Tasks on Hosts Chapter 7: Connection Brokering Module Mapping and Allocation Tasks Dedicated Allocation Mapping Dedicated Mappings (Thin Clients to Hosts) Dedicated Mappings (Thin Clients to Virtual Machines) Dedicated Mappings (Users to Hosts) Dedicated Mappings (Users to Virtual Machines) Delete All Dedicated Allocation Mappings of a Thin Client or a User Shared Mapping Creating Groups Mapping Domain and Local Security Groups Adding Windows Security Groups Map a User Group to a Shared Virtual Machine Group Delete All Shared Allocation Mappings for a User Spare Mapping Map a Thin client Group to a Spare Host Group Delete All Spare Allocation Mappings of a Host Group Sentral Administrator s Guide ix

10 Chapter 8: Switching Module Available Switching Module Modes Manage Spare Switching x8 Switching Supervisor View Supervisor Control Admin/KVM Switching Operations Switching C/Ports between Blades Switching Thin Clients Between Blades or VMs Switching Users Between Blades or VMs Chapter 9: Tasks Hierarchical View Sentral Node CCT Node Group Nodes Chassis Group Nodes Chassis Nodes A3100 Chassis Configuring the Chassis View Refresh Rate Monitoring Blades in Chassis Changing a Chassis Name or Alias Changing a Blade Alias Managing Blades in the Chassis View Rename LCD Blink LCD Unblink System Power Off OS Shutdown R4200 and R4300 Chassis Host Nodes Chapter 10: Host Agent Tasks Configure the Host Agent at the Client Update the Host Agent from the Client Configure Host Agent SNMP Configure Alerts on the Host Agent Edit Alerts on the Host Agent x ClearCube Technology, Inc.

11 Delete Alerts on the Host Agent Log Off the Host Agent Chapter 11: Thin Client and Thin Client Agent Logging in to a Host from a Thin Client Configuring Single Sign on from I9440 I/Port Configuring a Thin Client Agent Logging in to Thin Client Manager Configuring a Thin Client Agent from Thin Client Manager Changing Local Thin Client User Name and Password Retrieving Thin Client Information Using a Web-Based Thin Client Configuring the Thin Client Login Screen Understanding User Session States When Logging off Thin Clients Log Off Disconnect and the Sentral Follow Me Feature Appendix A: Troubleshooting What to Do First DNS Resolution Checks Ping Checks Problem occurred while loading Authentication Module Installation Issues An InstallShield error occurs that stops the installation Tomcat does not find the correct version of Java Runtime Environment on the machine Sentral components are not in Add/Remove Programs Application does not load after login screen Database Issues Unable to drop the previous CMS database from your MS SQL database server Error 4261: Database connectivity has been lost. Please close Sentral and Restart Tomcat 268 Troubleshooting MySQL Troubleshooting MS SQL Authentication Issues Sentral fails to authenticate with a valid username and password Error Code 4282 Problem occurred in loading Authentication module Sentral chassis serial numbers do not match Configuration/Operation Issues Renaming a Host does not appear to take effect Sentral does not recognize a replaced Management module Host Agent does not update Sentral Administrator s Guide xi

12 Configuration View of the Primary chassis not working properly Security groups missing in Configuration, Security, or Advanced Security screens Some nodes appear to be unavailable, even though they are listed in the Sentral database.275 RDP Thin Clients Won t Connect to Hosts Appendix B: Events and Alerts Appendix C: Uninstalling Sentral Appendix D: References Restarting Sentral Components Database Connectivity Notes Authentication Host Authentication Console and Host Agent Application Logon Server Authentication Primary Server Secondary Server Admin and Spare Daisy Chains Sentral Server Failover Behavior Primary and Secondary Servers Sharing the Same Database Alerts Sent During Failover Appendix E: Contacting Support xii ClearCube Technology, Inc.

13 Chapter 1: Introduction Sentral Version 5.8 contains the following new features: New graphical user interface Support for Xen hypervisor and Microsoft Hyper V Support for VMware ESX 3.5 Support for Wyse V10L and V90L ActivePerl host side requirement removed Improved Hierarchical view performance Improved Advanced Security interface Support for Class B IP ranges Support for: I9440 I/Port C7420 Digital Fiber C/Port F Digital Fiber Transceiver R1350 blades ClearCube Sentral Version 5.8 provides a single interface to manage your virtual desktop infrastructure and virtual machines, physical host (such as blades and computers), thin clients, and your network infrastructure. ClearCube Sentral builds on four generations of ClearCube management software in a single management platform with an extensive list of innovative new features. Sentral offers IT administrators one place to monitor and control their entire deployment of local and remote computing assets. With Sentral, ClearCube customers will continue achieving server-level availability (99.9% uptime) for end user computing. ClearCube Sentral is a software package that delivers proven cost reductions through unique features such as dynamic resource allocation, virtual desktop management, active health monitoring, and host switching and sparing. Sentral also offers these benefits across platforms, with support for other vendors host systems (that is, physical 1

14 computers, blades, virtual machines, and other computing devices) as well as virtualized desktops. Designed to scale from small businesses to large enterprises, ClearCube Sentral offers total control to IT departments everywhere. Contents of Sentral CD The ClearCube Sentral 5.8 installation CD contains the individual installers for the various components of the application. The server, console, and host agent installers are All-in-One installers that automatically check for and install the required software components needed for each major component. The Sentral installers include: Sentral 5.8 Console installer Sentral 5.8 Server Sentral 5.8 Console I83xx Admin Utility Sentral 5.8 host agent installer Sentral 5.8 host agent application (for hosts, or physical computers, blades, virtual machines, and other computing devices) I83xx Driver Sentral 5.8 thin client agent installers Sentral 5.8 thin client agent for Windows XPe Sentral 5.8 thin client agent for NeoLinux The Sentral console installer lets you install the Sentral server and the Sentral console, with options to configure a single system as the Sentral console and Sentral server. If I8330 I/Ports are used, the I83xx Admin Utility must be installed on only one Sentral console system. See Installing Sentral Server and Sentral Console on page 32 for more information. The Sentral host agent must be installed on each host that Sentral manages (that is, physical computer, blade, virtual machine, or other computing device). If there are I8330 I/Ports in your enterprise, install the I83xx Driver on each host to which an I8330 I/Port connects. See Installing Sentral Host Agents on Hosts and Virtual Machines on page 39 for more information. NOTE Do not install the I83xx Driver on a Sentral console system or on any other system that runs the I83xx Admin Utility. The Sentral thin client agent must be installed on each thin client (excluding I8330 I/Ports) that Sentral manages. The Sentral CD ROM includes installers for Windows 2 ClearCube Technology, Inc.

15 Chapter 1: Introduction XPe and for NeoLinux. You can use Neoware ezremote Manager to install thin client agents on NeoLinux thin clients. You can install Neoware ezremote Manager on the Sentral console system so you can deploy thin client agent to all NeoLinux thin clients from one location. You can install Windows XPe thin client agents locally or you can use Neoware ezremote Manager. See Preparing Thin Clients for Deployment on page 44 for more information. License Requirements Sentral requires a license file for operation. Every copy of Sentral is shipped with a 60-day fully functional temporary license that starts on the date of installation. When you are ready to register Sentral, visit the ClearCube Web site. If you do not obtain a license within 60 days of installing Sentral, you will no longer be able to log into Sentral. For more information, see Installing the Sentral License on page 53. Hardware and Software Requirements This section lists minimum hardware and software requirements for systems running Sentral Version 5.8 and related applications and hardware. Minimum System Requirements The following list assumes that the Sentral Console, the Database Server, and the Database server is installed on a computer dedicated to running that component. Sentral console 2.4 GHz processor 512 MB 2 GB HDD free space Sentral server 2.4 GHz processor 1 GB 2 GB HDD free space Database server 2.4 GHz processor 512 MB RAM Sentral Administrator s Guide 3

16 10 GB HDD free space Hosts running Sentral host agent 1.8 GHz processor 256 MB RAM 1 GB HDD free space ClearCube chassis R4300 RMM firmware version 52B12 or higher R4200 RMM firmware version 1.36 or higher Sentral console display Minimum display resolution of 800 x 600 (1024 x 768 recommended) Software Requirements Sentral installers automatically install all required software. If any required software is already installed on the system, Sentral installers do not overwrite the existing installation. The following list details each Sentral component with software requirements. Sentral server Java Software Development Kit (SDK) Version 1.5.0_08 FTP Server Apache Tomcat Sentral console Java SDK 1.5.0_08 I83xx Admin Utility (only if using I8330 I/Ports) NOTE The I83xx Admin Utility is not supported on Windows 2000 or Windows Vista. Database server One of the following SQL databases (the following are not included with Sentral Version 5.8): Microsoft SQL Server 2000 SP3a and SP4 4 ClearCube Technology, Inc.

17 Chapter 1: Introduction Microsoft SQL Server 2005 SP1 MySQL Server VM host systems (if VMs are used) One of the following VM host applications: Hyper-V VMware ESX Server versions 3.0, 3.0.1, and 3.5 VMware Server VMware Server Microsoft Virtual Server 2005 R2 SP1 Host Sentral Version 5.8 host agent BMC USB driver (A1410 blade only) I83xx Driver (I8330 I/Ports only) NOTE Do not install the I83xx Driver on any system on which the I83xx Admin Utility has been installed. NOTE The I83xx Driver supports Windows XP Professional only. J2RE 1.4.2_06 Thin clients Sentral Version 5.8 thin client agent Supported Operating Systems The following list details the supported operating systems for Sentral console, Sentral server, and Sentral host agents. Windows Vista Business Windows XP Professional with SP1 and SP2 NOTE ClearCube supports the English language version of Sentral Version 5.8 running German, Spanish, and French language versions of Windows XP and Windows Vista operating systems. Windows 2003 Server R2 Standard Edition Sentral Administrator s Guide 5

18 Supported Thin Clients Sentral supports the following thin clients: Wyse V90L Wyse V10L ClearCube I9420 I/Port ClearCube I9440 I/Port ClearCube C7420 Digital Fiber C/Port I8330 I8820 I8020 I8800 Eon e140 Eon e100 Capio One And additional Windows XP Embedded (XPe) thin clients Sentral Overview Sentral is comprehensive management software for virtual desktop infrastructures and centralized client computing infrastructures. Sentral combines the power of the previous ClearCube applications Switch Manager, Grid Center, Blade Manager, and Control Center into a single management platform, and offers much more. Sentral offers IT administrators one place to monitor and control their entire deployment of local and remote computing assets. Sentral also allows ClearCube customers to continue achieving server-level availability (99.9% uptime) for end user computing. Designed to scale from small businesses to large enterprises, ClearCube Sentral offers total control to IT departments everywhere. Sentral modules are managed by license key that are easily obtained online. In addition, Sentral is provided with a 60-day fully featured trial and setup license that allows complete access to every Sentral function and module. The 60-day time period starts when you install Sentral, and can be upgraded to a full license at any time after that. Sentral allows corporate administrators full control over the provisioning of computing power and its allocation to client devices. Limiting a user to a single host 6 ClearCube Technology, Inc.

19 Chapter 1: Introduction (for example, a computing device such as a traditional PC, laptop, or a virtual machine) has the potential to create imbalanced resource utilization. This is because while the same host or virtual machine (VM) may have more than enough capability for a light workload at a particular time, it may provide too little computing or memory capacity for more demanding tasks at other times. Sentral provides a single interface for all the typical resource monitoring tasks an enterprise IT Administrator needs to perform. This includes delivering software and driver updates to thin clients, monitoring the health of thin clients, and instrumentation on host resource usage. The Sentral dashboard provides a networkwide snapshot of key resource elements. Sentral automates a number of help desk and service tasks that require physical intervention with traditional legacy PCs. For instance, if a VM or other host becomes unavailable because of hardware or software failures, Sentral's sparing functionality allows an administrator to allocate a new VM or host to the end user almost immediately. If an administrator needs to perform maintenance on a host and needs to switch a user currently logged into the host to another host, he or she can do so using Sentral switching-over-ip functionality. Sentral manages all major components in a hosted client architecture. These components include: Hosts (typically physical computers or physical computers running virtual machines (VMs) VM host, or hypervisor, is the virtualization platform that enables multiple VMs to run on a physical host Thin clients, such as ClearCube I/Ports, at the users desktops Connection between a user s thin client and host ClearCube I94xx I/Ports or C/Port-based clients for high-performance graphics users Blade chassis User security model (permissions, privileges, and integration with Directory Services) Sentral Administrator s Guide 7

20 The following figure shows a typical Sentral deployment on an enterprise network. A Sentral Enterprise Hosts running Sentral host agent User accessing Sentral network thought browserbased remote access Secondary Sentral Server (Failover) User with session on VM host running on XPe thin client Sentral Database User with dedicated host running NeoLinux thin client agent Primary Sentral Server Firewall Sentral Console Administrator s C/Port External Internet Traffic Router Figure 1. Typical Sentral enterprise deployment Servers This section briefly describes each server in the Sentral environment. Servers described include: Primary Sentral server see Primary Sentral Server on page 9 Secondary Sentral server see Secondary Sentral Server on page 9 Sentral server failover see Failover Scenario Workflow on page 9 Sentral database server see Database Server on page 10 8 ClearCube Technology, Inc.

21 Chapter 1: Introduction Primary Sentral Server The Sentral Server is an application server that acts as an interface between the Sentral Console, the database server, and the systems managed by Sentral. It provides the ability to simultaneously service multiple Sentral Consoles. The Sentral Server also supports fault-tolerant failover to a Secondary Sentral Server. The main Sentral application logic is executed on this application server. Each Console node connects to and interacts with this server. The Primary server maintains the security model for the application and interacts with the each of the nodes in the Sentral environment, including the database that stores all of the characteristics, information, and logs related to the Sentral environment. Typically, only one Primary Sentral Server is used in a Sentral installation. When a Primary and Secondary Sentral Servers are configured, failover is provided from the Primary to the Secondary. Every transaction that is managed by the Primary Sentral Server includes a final synchronization step to ensure that the Secondary Sentral Server is always in lock step. Secondary Sentral Server The secondary Sentral server is a mirror image of the primary Sentral server. The secondary Sentral server receives one-way updates from the devices configured to communicate with primary and secondary Sentral servers. If there is a primary server failure, the secondary server takes over communications and becomes the primary with no loss of configuration information. The secondary server is optional. To configure the secondary server, provide a host name, fully qualified domain name, and an IP address in the Sentral configuration screen. For more information about the secondary server, see Using the Configuration Screen on page 89 and Table 6 on page 91. Failover Scenario Workflow In the event that a Primary server fails or goes offline, there is no need for any user interaction, and no re-login is required. Every client checks to see whether the Primary is alive or not before sending a request. If the Primary is down then it sends its information to the Secondary. If you have a primary and secondary database in your Sentral environment, you do not need to configure the databases for automatic failover. Provide a host name, fully-qualified domain name (FQDN), or an IP address for both servers and failover configuration is performed automatically. Some Sentral functionality works on non-clearcube systems. Certain Alerts that require WMI variables not provided on a non-clearcube system may not run as expected. Using the Sentral host agent UI, the Administrator can view all collected Sentral Administrator s Guide 9

22 WMI variables and determine whether a particular non-clearcube system is unable to report some of this information. Figure 1 on page 8 shows a typical Sentral deployment on an enterprise network. Database Server The Database Server hosts the Sentral database, which contains data about the hosts (such as physical computers, blades, and virtual machines) clients (thin clients), and users that are discovered on the Sentral network. The Database server is a Microsoft SQL Server or MySQL RDBMS that stores all of the information about the Sentral environment, including inventory information, logs, mapping information, health and status, security, and management information. For database redundancy, one database server is required for each Sentral server. Use one of the following databases: Microsoft SQL Server 2005 SP1 MySQL Server Sentral Console The Sentral Console is the main User Interface for the Sentral administrators. The Console provides access to the entire Sentral environment through a user friendly graphical user interface. Any number of Sentral Consoles can be installed on the network. Physical Hosts, Virtual Machine Hosts, and Thin Clients Host agents and thin client agents run on each host and thin client in your Sentral environment to enable so you can manage them in a Sentral environment. Host agent Runs on computing devices such as traditional PCs, blades, laptops, and on virtual machines. Required on every host that Sentral manages, including virtual machines. Thin client agent Runs on thin clients in your Sentral environment. Required on every thin client that Sentral manages. See Supported Thin Clients on page 6 for a list of supported thin clients. 10 ClearCube Technology, Inc.

23 Chapter 1: Introduction I8330 agent Runs on I8330 I/Ports. Each host to which an I8330 connects requires an I83xx driver, including virtual machines. Neoware Thin Clients and ezremote Manager The Sentral thin client agent requires Neoware ezremote Manager for installation on NeoLinux thin clients. Thin clients must be connected to the network and visible to the ezremote Manager before the Sentral thin client agent can be installed. For convenience, it is recommended to install ezremote Manager on the Sentral Console, but ezremote Manager can be installed before the Sentral Console, and the Clients can be deployed before installing other Sentral components. NOTE Installing the Sentral thin client agent using ezremote Manager removes the Grid Center Client. This should be taken into consideration when deploying a Sentral installation with thin clients. Thin Clients without Operating Systems I8330 I/Ports, I9420 I/Ports, I9440 I/Ports, and C7420 C/Ports do not use an embedded operating system, so they do not require the installation of a thin client agent. However, every host to which an I8330 will connect needs the I83xx Driver installed. NOTE The I83xx Driver is supported only on Windows XP. Virtual Machine Host If VMs are deployed, Sentral Version 5.8 requires one of the following virtualization applications to correctly recognize VMs: Hyper-V VMware ESX Server versions 3.0, 3.0.1, and 3.5 VMware Server VMware Server Microsoft Virtual Server 2005 R2 SP1 Sentral Administrator s Guide 11

24 Starting Quickly Perform the following steps: 1. Install Sentral. See Chapter 2 Installing ClearCube Sentral Version 5.8 on page Configure the Sentral console. See Setting Global Configurations for Sentral on page Discover users and devices. See Discovering Sentral Nodes on page Set up and populate groups. See Chapter 8 Switching Module on page Create mappings and allocations. See Chapter 8 Switching Module on page ClearCube Technology, Inc.

25 Chapter 2: Installing ClearCube Sentral Version 5.8 This section describes how to install Sentral. A Sentral installation includes these tasks: Installing and configuring your Sentral database Creating the Sentral database schema Opening network ports to allow Sentral communications Installing the Sentral Server and Console Installing Sentral host agents on each host you manage in your Sentral environment Installing the Sentral thin client agents on each thin client you manage in your Sentral environment Detailed procedures for these tasks follow. The simplest installation of Sentral Version 5.8 is to install a SQL database, the Sentral Server and all its components, and the Sentral Console all on one system. Before Installing Sentral Perform the following tasks before installing Sentral: Obtain your Sentral license. For more information, see Installing the Sentral License on page 53. Make any necessary network configurations. For more information, see Configuring DNS and DHCP for Clients That Do Not Auto-Register on page 14. Install a SQL database to hold your Sentral network data. For more information, see Install Your Sentral SQL Database on page 27. Uninstall previous versions of ClearCube software. For more information, see Uninstall Previous Versions of All ClearCube Software on page

26 Configure network ports. For more information, see Configuring Inbound Network Ports on page 21. Make any necessary configuration to VM Host virtualization platform. For more information, see Integrating Hypervisors and Virtual Machines in Sentral on page 59. Configuring DNS and DHCP for Clients That Do Not Auto- Register The following sections describe how to configure DNS and DHCP on Windows 2003 Server. If your Sentral environment includes other servers, perform the equivalent steps according the product documentation. If you have clients that do not auto-register with your DNS (such as NeoLinux clients or other clients that are do not use a Windows operating system), you need to configure your DNS and DHCP. To configure DNS, create forward lookup zones and reverse lookup zones. Sentral uses forward and reverse lookup zones to obtain client IP addresses. In Sentral Version 5.8, DHCP hands out IPs, gets a hostname, and should go to DNS and delete old records and populate new records when a lease expires for a DHCP client. Creating a DNS Forward Lookup Zone This section describes how to create a DNS forward lookup zone on Windows Server 2003 for thin clients and hosts in a selected domain. Perform the following steps. 1. Click Start > All Programs > Administrative Tools > DNS to open the dnsmgmt window. 14 ClearCube Technology, Inc.

27 Chapter 2: Installing ClearCube Sentral Version Right-click the Forward Lookup Zones folder and select New Zone to open the New Zone Wizard. Figure 2. The dnsmgmt window 3. Select the zone appropriate for your environment and then click Next. Figure 3. New Zone Wizard 4. Select the directory zone repilcation scope appropriate for your environment and click Next. Sentral Administrator s Guide 15

28 5. Type a zone name in the text box and then click Next. 6. Select the Dynamic Update appropriate for your environment. XPe and NeoLinux thin clients Select Allow both nonsecure and secure dynamic updates. Figure 4. Dynamic Update screen 7. Click Next, and then click Finish to create the Forward Lookup Zone. Creating a DNS Reverse Lookup Zone This section describes how to create a DNS reverse lookup zone on Windows Server 2003 for thin clients and hosts in a selected domain. Perform the following steps. 16 ClearCube Technology, Inc.

29 Chapter 2: Installing ClearCube Sentral Version If you have not already done so, click Start > All Programs > Administrative Tools > DNS to open the dnsmgmt window. 2. Right-click the Reverse Lookup Zones folder and select New Zone to open the New Zone Wizard. 3. Click Primary Zone and then click Next. 4. Select the directory zone repilcation scope appropriate for your environment and click Next. 5. Specify the reverse lookup zone by typing the zone s network ID or DSN zone name, and then click Next. Figure 5. The Reverse Lookup Zone Name window 6. Select the Dynamic Update appropriate for your environment. Sentral Administrator s Guide 17

30 XPe and NeoLinux thin clients Select Allow both nonsecure and secure dynamic updates. Figure 6. Dynamic Update screen 7. Click Finish to create the reverse lookup zone. You can now see the zone in the hierarchy. Configuring DHCP Server This section describes how to configure a DHCP server to work in Sentral Version 5.8 on Windows Server click Start > All Programs > Administrative Tools > DHCP to open the DHCP console. 2. Right-click the DHCP server and then click Properties. 3. In the DNS tab select the following items, as show in the following figure: Enable DNS dynamic updates according to the settings below Always dynamically update DNS A and PTR records Discard A and PTR records when lease is deleted 18 ClearCube Technology, Inc.

31 Chapter 2: Installing ClearCube Sentral Version 5.8 Dynamically update DNS A and PTR records for DHCP clients that do not request updates Figure 7. DHCP console 4. Click the Advanced tab, and then click the Credentials button. Figure 8. DHCP console Advanced tab Sentral Administrator s Guide 19

32 5. Type the name of the existing AD account that has administrative rights to update DNS. Figure 9. DNS dynamic update credentials screen Sentral Network Node Name Limitations Ensure that network node names conform to the following limitations, as described: Sentral does not recognize system names beginning with a number (digit from 0 to 9). This includes systems whose literal names are their IP addresses. This limitation is imposed by Apache Tomcat. Do not use the underscore character ( _ ) in system names. This is a restriction of RFC1035 and applies to all Internet-connected systems. Sentral limits labels for the names of all managed nodes to 20 characters or fewer. Enabling Systems for Remote Access In a Sentral environment there are a variety of host systems, or nodes, to which you can connect, including physical PCs, blades, virtual machines, and thin clients. You must enable remote access (through RDP) on all systems that are remotely accessed. The following steps assume that the devices you enable for remote access run Windows XP operating system. 1. Click Start > Control Panel and double-click System. 2. In the Remote tab, select Allow users to connect remotely to this computer in the Remote Desktop portion of the tab. 3. Click OK. 20 ClearCube Technology, Inc.

33 Chapter 2: Installing ClearCube Sentral Version 5.8 Configuring Inbound Network Ports The following sections describe the network ports that you must open for Sentral. Configuring Network Ports on Windows XP In a Sentral environment, you need to configure firewalls on nodes (including firewalls on Windows XPe-based thin clients) to allow communication. Depending on the nodes in the network, you might need to open additional ports. The following instructions explain how to open ports on hosts running Windows XP. 1. Click Start > Control Panel to open the Control Panel, then double-click Windows Firewall. 2. In the General tab, ensure that the On option is selected. 3. In the Exceptions tab, click Add Port to display the Add a Port window. 4. Table 1 and Table 2 detail each port that you must open. The tables contain the same information, which is listed in different orders for your convenience. Consult either table to specify the ports to open: a. Type a meaningful name for the firewall exception in the Name text box. b. Type the port number, as specified in the Port # column in Table 1 or Table 2, in the Port number text box. c. Select TCP or UDP as specified in Table 1 or Table 2. d. Click OK to save the firewall exception. Repeat Step 4 for all ports listed in Table Click OK to close the Windows Firewall window. The following tables list all inbound ports and nodes for Sentral. Open these ports on the receiving node. It is assumed that no nodes have any restrictions on transmission. Sentral Administrator s Guide 21

34 If there is a router between Sentral nodes, verify communication through the router on each port that Sentral uses. The following table lists all ports and sorts them by port number. This table contains the same information as Table 2, which is sorted by receiving node. Table 1. Inbound Ports Sorted by Port TCP/UDP Port # Receiving Node (Inbound) Application UDP 9 Host Agent Wake on LAN enable IP Directed Broadcasts on routers TCP 21 FTP Server FTP Server TCP 22 RMM SSH TCP 23 RMM / RMC RMC configuration (telnet) TCP 25 Server for Alerts TCP 69 Sentral Server TFTP TCP 80 RMM / RMC RMC communication TCP 137 Windows XP SP2, WinConnect 2.0 UDP 137 Thin Client Printer, file sharing support on Windows XPe thin client UDP 138 Thin Client Printer support on Windows XPe thin client TCP 139 Windows XP SP2 UDP 139 Windows WinConnect 2.0 UDP 161 Enterprise Mgmt. System thin client SNMP Neoware ezremote Manager Locatethin clients for software updates UDP 162 Enterprise Mgmt. System SNMP host to Sentral Console TCP/UDP 427 I94xx I/Port SLP Discovery TCP 443 I94xx I/Port Remote Web Client Access TCP 512 Thin Client Neoware ezremote Manager thin client management UDP 1027 I8330 I/Port Check/load firmware TCP 1433 SQL Server To SQL Database TCP 2000 I9440 I/Port Single sign on feature TCP 3306 MySQL DB Server MySQL Database TCP 3389 Host (RDP) Console UDP 4001 Thin Client For discovering thin clients TCP 5900 Host and Thin Client VNC Remote Control Neoware ezremote Manager Shadow thin clients UDP 6502 Host and Thin Client Discovery TCP 8004 Host Agent Sentral Host Agent 22 ClearCube Technology, Inc.

35 Chapter 2: Installing ClearCube Sentral Version 5.8 Table 1. Inbound Ports Sorted by Port (continued) TCP/UDP Port # Receiving Node (Inbound) Application TCP 8080 Sentral Server Web-Based Access TCP 8443 Sentral Server To Console via SSL TCP 9000 Thin Client Console UDP 9000 Thin Client Console TCP I8330 I/Port I83xx Admin Utility TCP I/8330 I/Port I83xx Driver TCP I8330 I/Port I83xx Driver UDP I8330 I/Port I83xx Admin Utility TCP I94xx I/Port Connection Management The following table lists all ports and sorts them by receiving node. This table contains the same information as Table 1, which is sorted by port number Table 2. Inbound Ports Sorted by Receiving Node TCP/UDP Port # Receiving Node (Inbound) Application UDP 9 Host Agent Wake on LAN enable IP Directed Broadcasts on routers TCP 3389 Host (RDP) Console TCP 5900 Host (Remote Control) VNC UDP 6502 Host Discovery TCP 8004 Host Agent Sentral Host Agent UDP 161 Thin client Neoware ezremote Manager Locate thin clients for software updates TCP 512 Thin client Neoware ezremote Manager thin client Management UDP 4001 Thin client For discovering thin clients TCP 5900 Thin client Neoware ezremote Manager Shadow thin clients UDP 6502 Thin client Discovery TCP 9000 Thin client Console UDP 9000 Thin client Console TCP I8330 I/Port I83xx Admin Utility TCP I/8330 I/Port I83xx Driver UDP I8330 I/Port I83xx Admin Utility Sentral Administrator s Guide 23

36 Table 2. Inbound Ports Sorted by Receiving Node (continued) TCP/UDP Port # Receiving Node (Inbound) Application TCP I8330 thin client I83xx Driver UDP 1027 I8330 thin client Check/load firmware TCP 2000 I9440 I/Port Single sign on feature TCP 443 I94xx Thin Client Remote Web Client Access TCP I94xx Thin Client Connection Management TCP/UDP 427 I94xx Thin Client SLP Discovery TCP 25 Server for Alerts UDP 161 Enterprise Mgmt. System SNMP UDP 162 Enterprise Mgmt. System SNMP Host to Sentral Console TCP 21 FTP Server FTP Server TCP 3306 MySQL DB Server MySQL Database TCP 22 RMM SSH TCP 23 RMM / RMC RMC configuration (telnet) TCP 80 RMM / RMC RMC communication TCP 69 Sentral Server TFTP TCP 8080 Sentral Server Web-Based Access TCP 8443 Sentral Server To Console via SSL TCP 1433 SQL Server To SQL Database TCP 137 Windows XP SP2, WinConnect 2.0 UDP 137 Windows Printer support on Windows XPe thin client UDP 138 Windows Printer support on Windows XPe thin client TCP 139 Windows XP SP2 UDP 139 Windows WinConnect 2.0 Configuring Network Ports on Microsoft Vista This section describes how to configure inbound and outbound network ports for Sentral clients that run on Microsoft Vista. Configuring Inbound Ports Table 1 on page 22 and Table 2 on this page list all of the inbound ports that you must open on a Sentral client running Microsoft Vista. 24 ClearCube Technology, Inc.

37 Chapter 2: Installing ClearCube Sentral Version 5.8 Configuring Outbound Ports To enable outbound communication in Microsoft Vista, you must specify the executables (using rules) that Windows Firewall with Advanced Security permits to communicate. Perform the following steps on Microsoft Vista to create rules for all of the executables in Table 3 on page Click Start > Control Panel > Administrative Tools. 2. Double-click Windows Firewall with Advanced Security. 3. In the left-hand pane, click Outbound Rules. Then click New Rule in the Actions panel to display the New Outbound Rule Wizard. 4. Under What type of rule would you like to create, select Program and then click Next. Figure 10. Creating a Program Rule in the Rule Wizard 5. Specify each executable that requires an open outbound port. Table 3 on page 26 lists each executable requiring an open port. Perform the following steps for each executable in Table 3: a. Select This program path. b. Click Browse and navigate to the executable location. c. Select the executable, click Open, and then click Next. Sentral Administrator s Guide 25

38 6. Select Allow the connection and then click Next. 7. Select the rule profiles appropriate for your environment, and then click Next. 8. Type a name for the rule and optionally type a description. Then click Finish. The rule is displayed in the Outbound Rules pane, as shown in the following figure. Figure 11. Outbound Rules Displayed in the Windows Firewall with Advanced Security Screen The following table lists all of the Server, Console, and host agent executables for which you must create an outbound rule. Table 3. Executables Requiring Outbound Communication Rules in Microsoft Vista Component Server C:\Program Files\Java\jre1.5.0_08\bin\java.exe Executable and Location C:\Program Files\Java\jre1.5.0_08\bin\javaw.exe %CATALINA_HOME%\webapps\CMSServer\WEB-INF\bin\https_call.exe %CATALINA_HOME%\webapps\CMSServer\WEB-INF\mc-wol.exe %CATALINA_HOME%\webapps\CMSServer\WEB-INF\ClientUpdates\SCHTASKS.exe 26 ClearCube Technology, Inc.

39 Chapter 2: Installing ClearCube Sentral Version 5.8 Table 3. Executables Requiring Outbound Communication Rules in Microsoft Vista Component Console C:\Program Files\Java\jre1.5.0_08\bin\java.exe Executable and Location C:\Program Files\Java\jre1.5.0_08\bin\javaw.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMSconsole.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMS\BladeBiosUpdate\ shutdown.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMS\ConsoleUpdate\7za.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMS\ConsoleUpdate\ safecopy.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMS\ConsoleUpdate\ snaptest.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMS\ConsoleUpdate\xcopy.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMS\bin\controlcenter\ mc-wol.exe C:\Program Files\ClearCube Sentral\ClearCube Sentral Console\CMS\BladeBiosUpdate\ WinPhlash\winPhlash.exe Host Agent C:\Program Files\Java\jre1.4.2_06\bin\java.exe C:\Program Files\Java\jre1.4.2_06\bin\javaw.exe Install Your Sentral SQL Database Prior to installing and using Sentral, you need a functional SQL database installed on your network to manage Sentral data. Supported databases are Microsoft SQL Server and MySQL Server (see Software Requirements on page 4). See the following URL for a link to the MySQL Web site: From the MySQL Web site, download the Microsoft Windows 32. ZIP format (16 Nov 2005, 33.6 M) file located in the Microsoft Windows section. Sentral Installation Overview The Sentral database, Sentral server, and Sentral console can be installed on the same system or on separate systems. Host Agents and virtual machines should be installed on systems other than the Sentral database, Sentral server, and Sentral console. ClearCube Sentral Version 5.8 can be installed on the following operating systems: Sentral Administrator s Guide 27

40 Windows Vista Business Windows XP Professional with SP1 or SP2 NOTE ClearCube supports the English language version of Sentral running German, Spanish, and French language versions of Windows XP and Windows Vista operating systems. Windows 2003 Server R2 Standard Edition Sentral includes All-in-One installers for the Sentral Server, Console, and host agent that check the target systems for installed components, and then install all the necessary pieces in a single pass. Using the All-in-One installer with its default settings is strongly recommended, as this greatly reduces the likelihood of introducing install-time configuration errors. The following component applications are required by Sentral, and are included with the All-in-One installers: Java SDK 1.5.0_08 Sentral Version 5.8 Server and Sentral Version 5.8 Console require JRE version 1.5.0_08. JRE 1.4.2_06 Sentral Version 5.8 host agent requires JRE version 1.4.2_06. FTP Server Sentral Version 5.8 Server requires the ClearCube FTP Server. Apache Tomcat Sentral Version 5.8 Server requires Apache Tomcat ClearCube Sentral Version 5.8 Server ClearCube Sentral Version 5.8 Console ClearCube Sentral Version 5.8 host agent This application is provided on the Sentral installation CD and is installed by the All-in-One host agent installer. TightVNC The TightVNC (Virtual Network Computing) client/server software package allows remote network access to graphical desktops. TightVNC is licensed under the GNU General Public License. TightVNC is used to implement device remote control, which is primarily an administration function. Installing TightVNC alone does not mean that hosts intended to host user sessions will be able to do so. User sessions use the Microsoft RDP protocol, and it must be enabled on the host that is to host user sessions. Begin your Sentral installation by copying the contents of the Sentral Version 5.8 installation CD to a network share visible to the systems where Sentral is to be installed, or directly to the systems themselves. Installation is faster and more reliable when files are copied directly to the systems. Sentral application installation should be performed in this order: 28 ClearCube Technology, Inc.

41 Chapter 2: Installing ClearCube Sentral Version Install and configure a SQL database 2. Install the Sentral server and console 3. Install the Sentral host agent and thin client agent Installing Sentral Database The following sections describe how to: Automatically create a Sentral database and schema using the Sentral installer CD ROM, or inject a schema into an existing database using the Sentral installer CD ROM. Manually create a Sentral database schema. See Manually Creating the Database Schema on page 29 for more information. Automatically Creating the Database during Sentral Installation The Sentral installer can: Automatically create a SQL database during installation OR If you have an existing Sentral database, Sentral installer can automatically inject a schema into your SQL database. Run the installer to perform either of these options. Manually Creating the Database Schema Sentral requires a SQL database to hold its data. Compatible databases include MS SQL Server and MySQL Server (see Software Requirements on page 4). You can manually create a schema to inject in an existing Sentral database, for example, if you do not have permission to modify the database. Perform the following steps to create the database schema for your Sentral database: Sentral Administrator s Guide 29

42 1. Using the software and installation procedures provided with your SQL database server, install the SQL database application. NOTE Neither MS SQL Server nor MySQL Server is provided with ClearCube Sentral, and must be obtained separately. For more information and a link to the MySQL Web site, use this URL: Download the file Microsoft Windows 32. ZIP format (16 Nov 2005, 33.6 M). 2. Copy the applicable SQL script for your database from the Sentral installation CD to the database system. Ensure that you use the correct script for your database. Database scripts are located in the top level of the Sentral installation CD in the Database Schema folder (X:/Database Schema), where X is the optical drive containing the installation CD ROM. The following two procedures provide easy methods to run the SQL script for your database. 3. For MS SQL Server 2000 Service Pack 3 and Service Pack 4: a. From the desktop, open the MS SQL script with a text editor. Copy the script contents. b. Click Start > Programs > Microsoft SQL Server > Query Analyzer to start MS SQL Query Analyzer. c. Paste the MS SQL script into the Query Analyzer window, as shown in Figure 12 on page 31. d. Click Run as shown in Figure 12 on page 31. e. As the script runs, watch the lower window for error messages. f. If no errors occur, verify that the Sentral database (named CMS database) has been created. Start the MS SQL Enterprise Manager as follows: Start > Programs > Microsoft SQL Server > Enterprise Manager g. Expand the database tree to verify that CMS Database is in the tree 30 ClearCube Technology, Inc.

43 Chapter 2: Installing ClearCube Sentral Version 5.8 Skip Step 4 and continue to Installing Sentral Server and Sentral Console on page 32. Run button Query Window Figure 12. MS SQL Query Analyzer Window 4. For MySQL Server: a. Start MySQL Server from the Start menu as follows: Start > Programs > MySQL Server 5.0 > MySQL Command Line Client b. In the command window, enter your MySQL Server password. c. At the mysql> prompt, enter source <literal_path_to_script><scriptname.sql> where <literal_path_to_script> is the literal path to the script (including drive identifier), and <scriptname.sql> is the script name. The command is case-sensitive and the.sql extension is required. For example: mysql> source e:\database Schema\MySQL\Sentraln.n.nMysql.sql where n.n.n is the Sentral version you are installing. When the script finishes running, the database schema is successfully set up. When you install the Sentral Server, database connectivity is established automatically by specifying the name of the SQL database system. When you configure the console, you provide the credentials to log into the database. Sentral Administrator s Guide 31

44 Installing Sentral Server and Sentral Console This section describes how to install Sentral server and console. NOTE If you install the Sentral host agent on the same computer as the Sentral server, you must install the Sentral server before you install the host agent NOTE During installation, the Sentral installer may appear to halt. If this happens, wait approximately one minute, then close any open windows on the desktop other than the installer dialog boxes. The Sentral Server requires administrator privileges for installation. To install the Sentral Server, perform the following steps: 1. Log into the system as Administrator. 2. Copy the setup.exe installer from the root directory of the installation CD to the designated Server computer. 3. Double-click setup.exe to start the installer. 4. In the Sentral All-in-One Install Screen (Figure 13 on this page), you are offered a choice to install the Sentral Server and the Sentral Console on this system. ClearCube Sentral 5.8 Administrator s Guide Readme Server and Console Installation Host Agent Installation Thin Client Agent Installation Database Schema Figure 13. Sentral Server All-in-One Install Screen The Sentral Server and Console can reside on the same system. You may install multiple Consoles, but install the Sentral Server no more than twice once as the Primary Server, and once as a Secondary Server. Check or un-check ClearCube Sentral Server Version 5.8 and ClearCube Sentral Console Version 5.8 to install the Server and Console as required. 5. Click Next to proceed. 32 ClearCube Technology, Inc.

45 Chapter 2: Installing ClearCube Sentral Version As the All-in-One installer proceeds, accept the installation defaults. 7. If a different J2RE version is already installed on the host, the installer displays a message indicating that the installed version is unsupported. Sentral Console does not support J2RE versions lower than the version in the installer. After the Java Runtime Environment (J2RE) is installed, you might be prompted to restart your system. Choose No. You should not restart your host until all the components are installed. If you restart your system before the installer has finished running, you will need to restart the installer after your system reboots. 8. When you reach the NT Service option dialog in the Tomcat installation shown in Figure 14 on page 33, check the NT Service box to enable loading Tomcat as a service. Must be checked Figure 14. Apache Tomcat Setup NT Service Checked 9. The Database Configuration screen, shown in the following figure, allows selecting the SQL database you just configured. The information entered in this screen sets up connectivity to the database. Figure 15. Database Configuration Screen Sentral Administrator s Guide 33

46 User Name Type the user name for the Sentral database administrator. Password Type the password for the database administrator. Database Server Type the database s host name or IP address. ClearCube recommends using a static IP address. Database Choose MySQL or SQL Server as appropriate for your environment. Create Database Select Yes to automatically load the schema you created previously (in Automatically Creating the Database during Sentral Installation on page 29 or in Manually Creating the Database Schema on page 29) into the Sentral database. 10. You are prompted to enter the names of the Primary and Secondary servers, as shown in the following figure. Both fields are auto-filled with the name of the system on which you are installing the Sentral Server application. You can specify Primary and Secondary servers now. Perform either of the following steps: Use the auto-filled default. You can configure another server later as either Primary or Secondary server. OR Manually specify the Primary server. You can specify the Secondary server now or later. For more information, see Using the Configuration Screen on page 89. Figure 16. Primary and Secondary Server Configuration 34 ClearCube Technology, Inc.

47 Chapter 2: Installing ClearCube Sentral Version If you chose to install Sentral Console on this system, the Internationalization screen is displayed, as shown in Figure 16. Select English (United States) and click Next. Figure 17. Internationalization Screen 12. This step is required only if there are I83xx I/Ports in your environment. Skip this step if you are not using I83xx I/Ports. When you reach the I83xx Admin Utility screen shown in the following figure, enter the name of the Sentral Console system you are currently installing, and then enter the name and password of a user on this system with administrator-level permissions. NOTE The I83xx Admin Utility is required only if you use I83xx I/Ports in your environment. Install the I83xx Admin Utility on no more than one system in your network. ClearCube recommends installing the I83xx Admin Utility on the Primary server. Figure 18. I83xx Admin Utility Screen Sentral Administrator s Guide 35

48 13. If you encounter the User checking error dialog, shown in the following figure, immediately perform the Tomcat Authentication procedure described in Configure Tomcat Authentication for Sentral Server on page 36. Do not exit the Sentral Installer or the I83xx Admin Utility Installer. Figure 19. Admin Utility Installer Error Dialog Once you have entered authentication credentials in Tomcat and restarted the Tomcat service, resume thei83xx Admin Utility installation. 14. When the installation process is completed, restart the system. After restarting your computer, you can launch ClearCube Sentral. Configure Tomcat Authentication for Sentral Server On each system where Apache Tomcat is installed as a service (as described in this guide), you need to configure authentication for the Console. This allows the Console to access the functionality in Tomcat when it logs into the Server. Tomcat authentication configuration must be performed before logging in to the Sentral Console. You can perform this action after installing Sentral Console and before you restart the system, or when you are ready to log into the Console for the first time. 1. From the Control Panel, select Administrative Tools, then double-click Services. 36 ClearCube Technology, Inc.

49 Chapter 2: Installing ClearCube Sentral Version Double-click Apache Tomcat. Select the Log On tab. The window shown in the following figure is displayed. Figure 20. Apache Tomcat Authorization Configuration 3. In the Log On tab, select This account: as the default logon parameter, and enter an account and password with Local Administrator privileges if using Local Workgroup authentication, or an account and password with domain membership if using Domain authentication for Sentral. 4. Click OK. The Services dialog box displays the following message: The account.\administrator has been granted the Log On As A Service right 5. Stop and then restart the Apache Tomcat service. a. Click Start > All Programs > Apache Tomcat > Stop Tomcat. b. Click Start > All Programs > Apache Tomcat > Start Tomcat. Console-Only Installation To install only the Sentral Console on a system, perform the following steps. NOTE During installation, the Sentral installer may appear to halt. If this happens, wait approximately one minute, then close any open windows on the desktop other than the installer dialog boxes. 1. Log in to the system as Administrator. Sentral Administrator s Guide 37

50 2. Copy the setup.exe installer from the root directory of the installation CD to the computer where you will install the Sentral Console. 3. Launch the setup.exe file. 7 7 Figure 21. Sentral Console All-in-One Install Screen 4. In the Sentral Setup Type screen, clear the following: FTP Server Tomcat ClearCube Sentral Server Version 5.8 As shown in Figure 21 on this page, the Console and its required component (Java Runtime Environment) are installed, but not the Server, Apache Tomcat, or the FTP Server. You can leave I8330 Support checked even if you do not plan to deploy I8330 I/Ports at this time. NOTE The I83xx Admin Utility is not supported on Windows Click Next, and accept the installation defaults. 6. After the JRE is installed, choose No. You should not restart your host until all the components are installed. 7. When the installation process is completed, restart the host. 8. You can test database connectivity from the main menu by clicking Setup > Configuration > Database Connectivity Test. A restart is required before launching ClearCube Sentral. Install the Console on as many systems as you require. You will need a separate license key for each Sentral Console. See License Requirements on page 3 for more information. 38 ClearCube Technology, Inc.

51 Chapter 2: Installing ClearCube Sentral Version 5.8 Installing Sentral Host Agents on Hosts and Virtual Machines Install the Sentral host agent on each host and on each virtual machine (VM) that you manage with Sentral. Virtual machine software is not provided with Sentral. ClearCube recommends copying the host agent installer, located on the Sentral CD ROM, onto the host or VM hard drive and installing locally. You can also copy the installer to a network share, and install from the network share. NOTE If you install the Sentral host agent on the same computer as the Sentral server, you must install the Sentral server before you install the host agent. For instructions about installing Sentral server, see Installing Sentral Server and Sentral Console on page 32. The Sentral host agent requires administrator privileges for installation. To install the Sentral host agent on a host, perform the following steps: 1. Ensure that you: Log in to the physical host or VM as an Administrator with installation privileges. For VMs only: Install and configure VM host application and VMs according to product documentation. For VMs only: Open ports that Sentral requires for communication, as specified in Table 1 on page Copy the setup.exe installer from the Sentral Client Software\Sentral host agent folder on the installation CD ROM to the host or VM. 3. Double-click setup.exe to launch the installer. 4. Except as noted in Step 6 on page 40, accept the installation defaults and licenses. NOTE The I83xx Driver is supported only on Windows XP. Sentral Administrator s Guide 39

52 7 Figure 22. Sentral host agent All-in-One Install Screen 5. If a different J2RE version is already installed on the host, the installer displays a message indicating that the installed version is unsupported. If the J2RE already installed on the host is a higher version, you can safely continue installation. The host agent does not support J2RE versions lower than the version in the installer. After the J2RE is installed, you might be prompted to restart your system. Click No. Do not restart the until all the components are installed. If you restart your system before the installer has finished running, you will need to restart the installer after your system reboots. 6. When you reach the TightVNC Select Additional Tasks Setup screen, shown in the following figure, ensure that the following items are checked: Associate.vnc files with TightVNC Viewer (default is checked) Register TightVNC Server as a system service (default is not checked) 40 ClearCube Technology, Inc.

53 Chapter 2: Installing ClearCube Sentral Version 5.8 Start or restart TightVNC service (default is not checked) Select Both Figure 23. TightVNC Select Additional Tasks Setup Screen 7. This step is required only if the host or VM connects to an I83xx I/Port. Skip this step if you are not using I83xx I/Ports. When you reach the I83xx Driver Password Screen shown in the following figure, it is recommended, but not required, to disable password protection on the driver. NOTE If you set a password now, you will need this password to remove or update the I83xx Driver. Checking Disable password protection removes password protection only on the driver. All other administrative and user password protection on the system remains unchanged. Recommended setting checked Figure 24. I83xx Driver Password Screen Sentral Administrator s Guide 41

54 The installer displays a black screen for several seconds before the I83xx Driver installation completes. A host or VM with the I83xx Driver installed shows a black logon desktop with the text I83xx Driver Blade Server Edition displayed at the top. 8. Restart the host or VM to complete installation. Installing BMC Drivers on A1410 Blades This section describes how to install drivers for the baseboard management controller (BMC) on ClearCube A1410 blades. Perform the following steps. NOTE Do not install the BMC driver on an A1410 blade while running an RDP session on the blade. NOTE To install the BMC driver on an A1410 blade, remove the blade from the chassis and attach a monitor and keyboard to the blade. 1. Copy setup.exe from the Sentral Client Software\Sentral host agent folder of the Sentral installation CD ROM to the host. 2. Double-click setup.exe to launch the installer. 3. Click Next from the Welcome screen to start the installation process. 4. Select BMC USB Driver and click Next. NOTE The BMC USB driver installation option is displayed only when you run the installer on A1410 blades. 5. Click Next to start the BMC driver installation. 42 ClearCube Technology, Inc.

55 Chapter 2: Installing ClearCube Sentral Version Select A1400 BMC and click Next. 7. Click Next again, and then click Finish to close the USBIO Installation Wizard and return to the InstallShield wizard. 8. From the InstallShield wizard, click No, I will restart my computer later and then click Finish. 9. To verify installation, open the Windows Device Manager to verify the BMC driver installation, as shown in the following figure. 10. After installing the BMC driver and host agent, run a discovery from Sentral console to display an A3100 chassis containing your A1410 blades in: Hierarchical view Management - A3100 Chassis screen Sentral Administrator s Guide 43

56 Preparing Thin Clients for Deployment Depending on the thin clients in your enterprise, there are different configuration tasks you can perform to enable Sentral to manage the thin clients. The following sections describe how to enable each type of thin client that Sentral supports. NOTE If the thin clients in your enterprise have pre-installed Sentral thin client agents, you do not need to install or re-install the thin client agent. Installing Thin Client Agents Thin clients that run Windows XPe and NeoLinux operating systems require the Sentral thin client agent. You can install the thin client agent on: XPe thin clients by running the Windows XPe installer located on the Sentral CD ROM. HP Neoware XPe and NeoLinux thin clients using ezremote Manager and the snap-in files located on the Sentral CD ROM. Snap-in files are customized files that ezremote Manger uses install thin client agents on Neoware thin clients. NOTE ezremote Manager is not provided in the Sentral installer. Download this application at You are required to register with Neoware to obtain an ezremote Manager license. Installing on Windows XPe Thin Clients This section describes how to install the thin client agent on the following thin clients: Wyse V90L ClearCube I8820 ClearCube I8800 Eon e140 Eon e100 Perform the following steps to install a thin client agent locally on a single thin client. 1. Log into the thin client as Administrator. 2. Ensure that: No Sentral software is currently installed on the thin client. 44 ClearCube Technology, Inc.

57 Chapter 2: Installing ClearCube Sentral Version 5.8 The thin client is powered on and set up as described in the thin client documentation. All necessary peripherals (including a keyboard, mouse, monitor, and optical drive) are attached to the thin client. 3. Turn off or disable the write filter. 4. I8800 I/Ports only I8800 I/Ports require additional drive space for thin client agent installation. Move the C:\Program Files\Java directory to a network share or delete the folder. These files are not required for I8800 I/Port operations. 5. Insert the Sentral Version 5.8 CD ROM in the attached optical drive. 6. Locate the appropriate XPe thin client installer directory, as shown in the following list: For V90L: D:\Thin Client\ENG\XPE\Installer For all other thin clients listed in this section: D:\Thin Client\ENG\XPE\V90L_Installer where D is the optical driver letter. 7. Copy the entire installer directory to a volume that is visible to the thin client, such as a network share or a USB key drive plugged into the thin client. 8. Double-click setup.exe located in the Installer directory to install thin client agent. a. Click Next. b. Click Yes to acknowledge the license agreement. c. Click Finish. d. Type the name of the Sentral Primary Server and Secondary Server. Type the name of primary server in both fields if you do not have a secondary server. e. Click Finish to restart the thin client. 9. I8800 I/Ports only Optionally, move the C:\Program Files\Java folder from the network share back to the I8800 I/Port if you previously moved the directory. 10. Turn on or enable the write filter and the thin client restarts automatically. Your thin client agent installation is complete. Sentral Administrator s Guide 45

58 Installing on Neoware Windows XPe Thin Clients Use ezremote Manager to install thin client agents on Neoware XPe thin clients, including the following: ClearCube I8820 ClearCube I8800 Eon e140 Eon e100. NOTE ezremote Manager is not provided in the Sentral installer. Download this application at You are required to register with Neoware to obtain an ezremote Manager license. Perform the following steps: 1. Ensure that: ezremote Manager is installed according to product documentation. No ClearCube or GridCenter software is installed the thin clients on which you are installing the thin client agent. NOTE If you previously installed any ClearCube or GridCenter software on thin clients, you must remove the software in the same way you installed it. That is, if you manually installed the software, you must manually remove it. If you used ezremote Manager to install the software, you must use ezremote Manager to remove it. Thin clients are powered on and set up as described in the thin client documentation. You have the password or passwords for all thin clients you are accessing. 2. Copy the entire Windows XPe installer directory to an accessible location, such as a network drive. The installer directory is located on the Sentral CD ROM in the following location: D:\Thin Client\ENG\XPE\ezRM where D is the optical drive letter. 3. From the ezremote Manager Actions menu, click Assets. 4. Click Password and type the password for the thin clients you are updating. 5. Select the thin clients to receive the snap-in. 6. Click the Snapin Manager icon (the icon with the red plus mark) and browse to the snap-in. Click OK to apply the snap-in containing the thin client agent. 46 ClearCube Technology, Inc.

59 Chapter 2: Installing ClearCube Sentral Version 5.8 Installing on Neoware NeoLinux Thin Clients Use ezremote Manager to install thin client agents on Neoware NeoLinux thin clients, including the following: I8020 Eon e140 Eon e100 Capio One NOTE ezremote Manager is not provided in the Sentral installer. Download this application at You are required to register with Neoware to obtain an ezremote Manager license. Perform the following steps: 1. Ensure that: ezremote Manager is installed according to product documentation. No ClearCube or GridCenter software is installed the thin clients on which you are installing the thin client agent. NOTE If you previously installed any ClearCube or GridCenter software on thin clients, you must remove the software in the same way you installed it. That is, if you manually installed the software, you must manually remove it. If you used ezremote Manager to install the software, you must use ezremote Manager to remove it. Thin clients are powered on and set up as described in the thin client documentation. You have the global password for the thin clients you are accessing 2. Copy the entire NeoLinux installer directory to an accessible location, such as a network drive. The installer directory is located on the Sentral CD ROM in the following location: D:\Thin Client\ENG\Linux\gc\usr\local\IPORT-CLIENT where D is the optical drive letter. 3. From ezremote Manager, select Neoware Appliances in the left pane. 4. From the Actions menu, click Assets. 5. Click Password and type the global password for all of the thin clients you are updating. 6. Select the thin clients to receive the snap-in. Sentral Administrator s Guide 47

60 7. Click the Snapin Manager icon (the icon with the red plus mark) and browse to the snap-in. Click OK to apply the snap-in containing the thin client agent. Configuring DHCP Server for Wyse V10L Thin Clients To enable Sentral to manage V10L thin clients, you must perform the following steps in the sequence listed: 1. Add predefined options to your DHCP server settings, as described in Adding Predefined Options to DHCP Settings on page Add these predefined options to the DHCP server Scope Options, as described in Add Predefined Options to DHCP Scope on page Configure and run the V10L utility on the Sentral FTP server, as described in Running V10L Utility on Sentral FTP Server on page 52. The figures in the following sections show how to perform these steps on Windows Server If you are using a different operating system, perform the equivalent steps for that operating system. Adding Predefined Options to DHCP Settings You must add predefined options to your DHCP server settings to enable Sentral to discover Wyse V10L thin clients. By default these tags are not present in DHCP scope options. This section lists each predefined option to add and describes how to perform the task. Repeat the steps for each predefined option listed in Table 4 on page 48. The following table details the predefined options to add to the DHCP server. Each heading corresponds to a field or drop-down box in the dialog boxes shown in Step a on page 50 and Step b on page 50. Table 4. DHCP server predefined options required for V10L integration Predefined Option Name Purpose Data Type Code Description Field Value FTPServer Specifies Sentral FTP server for V10L thin client String 161 Add any meaningful description here. Static IP address of Sentral FTP server, in the format nnn.nnn.nnn.nnn. FTP Root Location where Wyse FTP configuration utility is installed String 162 Add any meaningful description here. V10L FTP User Name Sentral FTP server user name String 184 Add any meaningful description here. Specify the Sentral FTP server user name in this field. Password Password for Sentral FTP user String 185 Add any meaningful description here. Specify the Sentral FTP password in this field. 48 ClearCube Technology, Inc.

61 Chapter 2: Installing ClearCube Sentral Version 5.8 Perform the following steps to create the predefined option described in Table Click Start > Settings > Control Panel > Administrative Tools > DHCP to open DHCP manager. 2. In the leftmost pane, select the DHCP server for the subnet that the V10L thin clients are on. 3. Select Action > Set Predefined Options to display the Predefined Options and Values dialog box. Sentral Administrator s Guide 49

62 4. Create predefined options and specify values for each option in Table 4. Perform Step a and Step b for each option. a. Click Add to display the Option Type dialog box. Specify values for a predefined option, and then click OK to open the Predefined Options and Values dialog box. b. From the Option Name drop-down box, select the option you created in the previous step. c. In the String text box, type the value for the option (listed in Table 4) and then click OK. Repeat Step 4 for each predefined option listed in Table 4, and continue to the following section. Add Predefined Options to DHCP Scope This section describes how to add the V10L thin client predefined options you created in Adding Predefined Options to DHCP Settings on page 48 to the DHCP scope. A DHCP scope is a range of IP addresses available to lease or assign to DHCP clients or services. Perform the following steps: 50 ClearCube Technology, Inc.

63 Chapter 2: Installing ClearCube Sentral Version If you have not already opened DHCP manager, click Start > Settings > Control Panel > Administrative Tools > DHCP. 2. Expand the DHCP server for the subnet that the V10L thin clients are on. 3. Right-click Scope Options and select Configure Options. 4. From the Scope Options dialog box, specify string values for each predefined value you created in Adding Predefined Options to DHCP Settings on page 48. a. Select one of the predefined options you created in the previous section. b. In the String value text box, type the option value listed in the Value column in Table 4. c. Click OK. Sentral Administrator s Guide 51

64 5. Repeat Step 4 for each predefined option listed in Table 4, and continue to the following section. Running V10L Utility on Sentral FTP Server This section describes how to configure and run the Wyse.bat utility. The Wyse.bat utility enables Sentral FTP server to interact with V10L thin clients. Perform the following steps to run Wyse.bat: 1. Ensure that you have performed all the steps described in Adding Predefined Options to DHCP Settings on page 48 and Add Predefined Options to DHCP Scope on page Navigate to the Utility for Wyse Ftp Configuration.rar file, located in the following directory on the Sentral Version 5.8 CD ROM: \Sentral 5.8\Wyse configuration utility\ 3. Uncompress Utility for Wyse Ftp Configuration.rar to the Sentral FTP server. By default, Sentral FTP server is located in the following directory: C:\Program Files\ClearCube Sentral\FTPServer 4. Ensure that a directory named V10L does not exist in the FTPServer directory. If you have created a directory named V10L in that location, remove or rename it. 5. Open Wyse.bat with a text editor and change the values in the file so they are appropriate for your environment. The following list identifies each set line in the file. hostname Static IP address or host name of FTP server port FTP server port (21 by default) username User name for FTP server user password Password for FTP server user CMSAddress IP address of the Primary Sentral server in the format nnn.nnn.nnn.nnn CMSPort Port on which Sentral server is running (8080 by default) 6. Double-click Wyse.bat to run the utility. To verify successful configuration, ensure that a V10L directory is added to the FTPServer directory. 7. Restart your V10L thin client to display a Sentral thin client login screen. 52 ClearCube Technology, Inc.

65 Chapter 2: Installing ClearCube Sentral Version 5.8 Configuring Clientless and Web based Host Access Using a Web based interface, you can: Enable host users to access hosts through a Web browser Configure thin clients Configure the Web based thin client interface See Configuring a Thin Client Agent on page 255 for more information. Installing the Sentral License The following sections describe how to obtain and install your Sentral license. Obtaining a Permanent License Key To obtain permanent Sentral license key, perform the following steps: 1. Go to the following URL: 2. Complete all customer contact information fields. 3. Complete all order information fields with the information from your packing slip (see the following figure). 4. Enter the number of users. 5. Click Submit. An containing the license key will be sent to the address entered on the Web page. If you do not have the Sentral purchase order or sales order available, contact your Account Executive or contact ClearCube Technical Support for assistance. See Appendix E, Contacting Support, on page 291 for information about how to contact Technical Support. Sentral Administrator s Guide 53

66 Every license is specific to a machine name. You need a separate license for each Sentral Server and Sentral Console that you deploy. Figure 25. Required Fields from Packing Slip Installing the Permanent License Key After registering for a license key on the ClearCube Web site and receiving the containing the license key, perform the following steps to install the license key: 1. In the Login pop-up window, click the License Key link. The ClearCube Sentral License dialog box is displayed. 54 ClearCube Technology, Inc.

67 Chapter 2: Installing ClearCube Sentral Version Enter the license key. 3. Click Submit. 4. Restart the console. The Welcome screen changes, as shown in Figure 26 on page 55. The new Welcome screen shows which modules have been purchased and activated. The Trial License Welcome screen displays how many days are left on your trial license. A new license key can be re-entered from the Login screen at any time. Trial License Welcome Screen Permanent License Welcome Screen Figure 26. License Welcome Screens Upgrading from Sentral 5.6 The following sections describe: How to export and import existing Sentral configuration settings. Uninstalling previous versions of ClearCube Sentral software and component applications. How to add I8330 support to an existing Sentral installation. See Adding I8330 Support to Sentral Installations on page 57 for more information. How to upgrade Sentral Console and Server from version 5.6 to version Version 5.8. See Upgrading Sentral Console and Server on page 57 for more information. Sentral Administrator s Guide 55

68 How to upgrade Sentral host agent from version 5.6 to Version 5.8. See Upgrading Sentral Host Agent on page 58 for more information. Exporting Configuration Settings You can export any existing Sentral Version 5.0, 5.5, or 5.6 configuration settings to an XML file, and then import the configuration setting to your upgraded version of Sentral. Perform the following steps to export your existing configuration settings. NOTE You can only export and import configuration settings on Sentral Version 5.7 and Version From the main menu, click Setup > Configuration. 2. From the toolbar, click Configuration Export ( ) to display the Save dialog box. 3. From the Save dialog box, browse to a location to save the XML file and specify a file name. Click Save and then click OK. 4. Click File > Exit to exit Sentral and then restart the computer. See the following section for instructions about importing your configuration settings. Importing Configuration Settings Perform the following steps to import saved Sentral configuration settings. 1. From the main menu, click Setup > Configuration. 2. From the toolbar, click Configuration Import ( ). Sentral display the following message: This operation will overwrite the Server Configuration file. settings. Do you want to continue? Click Yes to display the Open dialog box. 3. From the Open dialog box, browse for the configuration XML file. Select the file and click Open or double-click the file. 4. Click OK to dismiss the confirmation message. 56 ClearCube Technology, Inc.

69 Chapter 2: Installing ClearCube Sentral Version 5.8 Uninstall Previous Versions of All ClearCube Software Before installing Sentral Version 5.8, uninstall all Sentral software below Version 5.8 from all systems. NOTE In some cases, ClearCube software uses the name CMS. Ensure that you remove any CMS software. If you are currently using Sentral 5.6, you can upgrade to version Version 5.8 as described in Upgrading from Sentral 5.6 on page 55. For information about uninstalling Sentral, see Appendix C, Uninstalling Sentral, on page 279. Adding I8330 Support to Sentral Installations If you are updating Sentral to add I8330 support only, run the Sentral console installer on each Sentral console system, and only select the I8330 support option. Run the Sentral host installer on each host or VM to which an I8330 will connect, and only select I8330 support. Remember to restart each system after installation. For more information, see Installing Sentral Server and Sentral Console on page 32 and Installing Sentral Host Agents on Hosts and Virtual Machines on page 39. Upgrading Sentral Console and Server This section describes how to upgrade Sentral Console and Sentral Server from version 5.6 to version Version 5.8. NOTE Sentral Version 5.8 does not require the Perl modules that previous versions of Sentral required. Upgrading to Version 5.8 does not remove any existing Perl modules. It is not necessary to remove Perl from any system in your Sentral Version 5.8 environment; however, you can safely remove Perl manually. 1. Click Start > All Programs > Apache Tomcat > Stop Tomcat to stop the Tomcat service on the computer running Sentral. 2. Insert the ClearCube Sentral Version 5.8 CD-ROM in your CD-ROM drive. When the installer menu is displayed, click Server and Console Installation to start the upgrade. 3. Depending on the security settings on your computer, Windows might display a warning dialog box when the installer starts. If a Security Warning dialog box is displayed, click Run to start the setup.exe executable file. 4. Select the options appropriate for your installation. ClearCube recommends accepting all default settings. 5. Restart your computer when the upgrade is complete. Sentral Administrator s Guide 57

70 6. To start Sentral console, click Start > All Programs > ClearCube Sentral Console > ClearCube Sentral Console Version 5.8. Sentral displays the ClearCube Sentral Console login window. 7. Click the License Key link in the lower-right portion of the dialog box to apply your existing Sentral 5.5 license and complete your upgrade. Upgrading Sentral Host Agent This section describes how to upgrade Sentral host agent from version 5.6 to version Version 5.8. NOTE Previous versions of Sentral and the host agent (previously, Blade Client) required Perl and Perl plugins. Sentral Version 5.8 and the host agent do not require Perl. If you are upgrading Sentral and have Perl or Perl plugins on your host, you can leave them. 1. Insert the ClearCube Sentral Version 5.8 CD-ROM in your CD-ROM drive. When the installer menu is displayed, click Host Agent Installation. 2. Depending on the security settings on your computer, Windows might display a warning dialog box when the installer runs setup.exe. If Windows displays Security Warning dialog box, click Run to start the setup.exe host agent executable file. Figure 27. Security Warning host agent 3. A message is displayed indicating that there is a host agent already on the computer. Click Yes to continue, and then click OK when the successful installation message is displayed. 4. Restart your computer to complete host agent installation. 58 ClearCube Technology, Inc.

71 Chapter 2: Installing ClearCube Sentral Version 5.8 Upgrading Sentral Thin clients This section describes how to upgrade the Sentral Version 5.6 Blade Client to Sentral Version 5.8 thin client agent. 1. Insert the Sentral Version 5.8 CD-ROM in your optical drive. From the installer menu, click Thin Client Agent Installation to open the Sentral thin client agent folder. 2. From the Sentral thin client agent folders, open the folder corresponding to the operating system that your thin clients run (that is, XPe or NeoLinux): For thin clients running XPe, open \Thin Client\ \ENG\XPE For thin clients running NeoLinux, open \Thin Client\ \ENG\Linux 3. Turn off or disable the thin client s write filter. See your thin client documentation for instructions about the write filter. 4. Open the UPDATE folder, and double-click setup.exe to start the installer. 5. Depending on the security settings on your computer, Windows might display a warning dialog box when the installer starts. If Windows displays a Security Warning dialog box, click Run to start installation. 6. The installer displays a message indicating that the thin client agent was upgraded successfully. Click OK to dismiss the message. 7. Flush the thin client s write filter, and then enable the write filter. The thin client restarts automatically. See your thin client documentation for information about the write filter. Integrating Hypervisors and Virtual Machines in Sentral The following sections describe how to integrate the following virtual machine hypervisors into a Sentral environment: ESX Server Xen hypervisor Microsoft Hyper V Integrating ESX Hypervisor You can manage ESX Server virtual machines in your Sentral environment by enabling ESX Server to communicate with Sentral over HTTP. The following sections Sentral Administrator s Guide 59

72 describe how to enable HTTP on different ESX Server versions. See and how to integrate ESX virtual machines into your Sentral environment. Enabling ESX Server 3.5 to Communicate with Sentral After installing ESX Server 3.5, edit the Http Reverse Proxy service configuration file and then restart the hostd process (the VMware host daemon) as described in the following steps. 1. Log in to the ESX Server service console as the root user. 2. From the ESX Server command line, change directories to /etc/vmware/hostd. 3. Use a text editor to open the proxy.xml file. 4. Navigate to the list of endpoints in the file (identified by the <EndpointList> tag) that contains settings for the Web service supporting the ESX SDK. The nested tags should be similar to the following example: <e id= 1 > <_type>vim.proxyservice.namedpipeservicespec</_type> <accessmode>httpswithredirect</accessmode> <pipename>/var/run/vmware/proxy-sdk</pipename> <servernamespace>/sdk</servernamespace> </e> 5. Change the accessmode to httpandhttps. The line should appear as follows: <accessmode>httpandhttps</accessmode> 6. Save and close the file. 7. Restart the vmware-hostd process by typing the following command: service mgmt-vmware restart Enabling ESX Server 3.0.X to Communicate with Sentral After installing ESX Server 3.0.x, edit the ESX Server configuration file as described in the following steps. 1. Open config.xml, located in the /etc/vmware/hostd/config.xml directory on ESX Server. 2. Locate the <proxydatabase> tag within the <http> tag. Use a text editor to add the following text to the contents of the <proxydatabase> tag: <server id="1"> <namespace> /sdk </namespace> <host> localhost </host> 60 ClearCube Technology, Inc.

73 Chapter 2: Installing ClearCube Sentral Version 5.8 <port> 8085 </port> </server> 3. Remove the following line: <redirect id="2"> /sdk </redirect> 4. Save the config.xml file. 5. Restart the VMware Infrastructure SDK Management Service by invoking the following command from the ESX Server command line: service mgmt-vmware restart Integrating Xen Hypervisor Perform the following steps to integrate Xen hypervisor in Sentral. 1. On the computer running Xen hypervisor, log in as the root user. 2. Navigate to the /etc/xen/ directory and open the xend-config.sxp file with a text editor. 3. Specify the IP address of the Xen hypervisor you are integrating in Sentral. In the last line of the following example, the IP address is shown as nnn.nnn.nnn.nnn, followed by a colon (:) and the default port 9363 (for brevity, only a portion of the file is shown in the following example). Replace the IP address in the file you are editing with the IP address of the Xen hypervisor in your environment.... # Example: listen on TCP port 9363 on all interfaces, accepting connections # only from machines in example.com or localhost, and allow access through # the unix domain socket unconditionally: # # (xen-api-server ((9363 pam '^localhost$ example\\.com$') # (unix none))) # # Optionally, the TCP Xen-API server can use SSL by specifying the private # key and certificate location: # # (9367 pam '' /etc/xen/xen-api.key /etc/xen/xen-api.crt) # # Default: (xen-api-server ((nnn.nnn.nnn.nnn:9363 none))) Navigate to the /etc/xen/ directory and open the xend-config-xenapi.sxp file with a text editor. Sentral Administrator s Guide 61

74 5. Remove the comment indicator (#) from the (xen-api-server ((9363 none))) line so it appears as shown in the last line of the following example (for brevity, only a portion of the file is shown):... # Example: listen on TCP port 9363 on all interfaces, accepting connections # only from machines in example.com or localhost, and allow access through # the unix domain socket unconditionally: # (xen-api-server ((9363 none))) Restart the computer running Xen hypervisor. Integrating Virtual Machines in Sentral The following sections describe how to integrate ESX, Xen, and Hyper-V virtual machines in Sentral. Integrating ESX and Xen Virtual Machines Perform the following steps to integrate existing ESX or Xen virtual machines in Sentral. 1. Ensure that you have integrated a hypervisor in your Sentral environment: For ESX: see Integrating ESX Hypervisor on page 59 For Xen: see Integrating Xen Hypervisor on page Check the connection between the hypervisor and Sentral: a. Navigate to the Host Management screen: For ESX: from the main menu, click Management > Virtual Machines > ESX Hosts. For Xen: from the main menu, click Management > Virtual Machines > Xen Hosts. b. Select and then right-click a VM. For ESX: select Add ESX Host Information from the right-click menu. For Xen: select Add Xen Host Information from the right-click menu. 62 ClearCube Technology, Inc.

75 Chapter 2: Installing ClearCube Sentral Version 5.8 c. Select and right-click the VM again and select Check Connection in the right-click menu. Sentral displays a success confirmation dialog box. If it does not, repeat this procedure from the beginning to ensure that you integrated the hypervisor correctly. 3. From the Host Information screen, select and right-click the host and select Retrieve Information in the right-click menu. Sentral displays registered VMs on the host in the Hierarchical menu. 4. This step is for ESX VMs only. For Xen VMs, skip this step. If the Host contains unregistered VMs: a. Right-click the Host in the Hierarchical view and select Register the VMs to display a table of unregistered VMs. b. Select and right-click a VM to register in the lower portion of the screen and select Register VM on a Host. c. Click OK to close the success confirmation dialog box. The VM is now display in the Hierarchical view as an offline VM. 5. Configure or reconfigure VMs as appropriate for your environment and add them to a group as described in Spare Mapping on page Allocate the Sentral VM group to a user group as described in Map a User Group to a Shared Virtual Machine Group on page 213. NOTE You must register a VM to add it to a pool. For more information about registering VMs, Registering ESX VMs in the Sentral Database on page 163. Integrating Hyper V Virtual Machines Perform the following steps to integrate Hyper V virtual machines in your Sentral environment. 1. Install Microsoft Hyper V according to the product documentation. 2. Install the Sentral host agent on each virtual machine you will manage with Sentral. To install the host agent on a virtual machine, perform the same steps provided for installing the host agent on a physical host. See Installing Sentral Host Agents on Hosts and Virtual Machines on page 39 for more information. 3. After installing the host agent on each virtual machine, run a Sentral discovery on the subnet or subnets that the virtual machines are on. See Discovering Sentral Nodes on page 109 for information about how to run a discovery. Sentral Administrator s Guide 63

76 64 ClearCube Technology, Inc.

77 Chapter 3: Starting with Sentral Sentral Version 5.8 provides an easy-to-understand graphical user interface for management of your ClearCube chassis, host, user port, and software assets. The following figure shows the Sentral console dashboard and identifies the major interface components. Hierarchical View Main Menu Utilization Charts View Menu Figure 28. Sentral Dashboard 65

78 Sentral Console Main Menu This section describes the main menu in the Sentral console graphical user interface. The following list details the main menu and each submenu. File Logoff Exit Edit Advanced Search Set current screen to home Configuration Wizard Setup Configuration Security Update Console Management Dashboard Hosts All Hosts AMT Hosts PCoIP Hosts Thin Clients Virtual Machines All Virtual Machines ESX Hosts Chassis R-Series Chassis C/Ports Groups A-Series Chassis 66 ClearCube Technology, Inc.

79 Chapter 3: Starting with Sentral Views Users Connection Brokering Allocation Switching Thin Clients Users C/Ports Health & Status Hosts Thin Clients Virtual Machines Chassis Alerts View Alerts Configure Alerts View Deployed Alerts Reports Inventory Alerts Custom Reports Equipment History Device Accessibility Hierarchical View The following sections describe the Hierarchical view and its features and provide examples of each icon in the menu. Sentral Administrator s Guide 67

80 Using Hierarchical Node Right-Click Menus The Hierarchical view, shown in the following figure, provides a visual representation of nodes in the Sentral enterprise. Similar to performing actions on nodes in Sentral screens, you can right-click any node to open a menu of tasks to perform on the node. Figure 29. The Hierarchical view showing enterprise nodes & right-click menu From the Hierarchical view, you can display all of the nodes in your Sentral enterprise, or restrict the view to display nodes on one or multiple subnets. See Discovering Sentral Nodes on page 109 for more information. Hierarchical View Icons The Hierarchical view displays discovered nodes in a Sentral environment. An icon containing an X represents an offline node (a node that has not reported to the Sentral console in a specified timeout period). The following table shows the icons displayed in the Hierarchical view. 68 ClearCube Technology, Inc.

81 Chapter 3: Starting with Sentral Table 5. Hierarchical View Icons Primary or Secondary Chassis Tertiary or R4200 Chassis R series chassis group R series chassis group offline Group Active Directory group BMC/A3100 chassis User Thin client Thin client offline I9440 thin client I9440 thin client offline I9420 thin client I9420 thin client offline Virtual machine (Vendor noted in display) Virtual machine offline (Vendor noted in display) R Series host R Series host offline A Series host A Series host offline ESX Host ESX Host offline A Series host with V5140 Quad Host A Series host with V5140 Quad Host offline A Series host with V5120 Dual Host A Series host with V5120 Dual Host offline Host other than an A series or R series host Host other than an A series or R series host offline Sentral Administrator s Guide 69

82 Host with AMT where only an AMT discovery has been performed. If the AMT host has a host agent installed, this icon is replaced by a host specific icon after you run a discovery on a subnet. For more information about setting timeout values for nodes, see the Discovery Configuration section of Table 6 on page 91 and the Timeout Value sections of Table 10 on page 121, Table 12 on page 136, Table 13 on page 152, Table 14 on page 156, and Table 16 on page 166. Using Right-Click Menus to Perform Tasks on Nodes in Sentral Screens The Sentral console displays tables to present detailed information about many nodes, such as chassis, thin clients, and users. To perform actions on nodes displayed in tables, you can: Right-click a node to perform an action on it, as shown in the following figure. Figure 30. Example of a right-click menu after selecting a node in a table OR Right-click an empty space in the table to perform an action on all the nodes or multiple nodes in the table, as shown in the following figure. Figure 31. Example of a right-click menu after right-clicking an empty space 70 ClearCube Technology, Inc.

83 Chapter 3: Starting with Sentral Menu Buttons The following figure shows the main buttons below the main menu Previous Screen 2. Next Screen 3. Refresh Current Screen 4. User Home Screen 5. Help Figure 32. Menu buttons The following list describes each button identified in the previous figure. Previous Screen Click this button, shown in Figure 32, to navigate to the previous Sentral screen. Next Screen After clicking the Previous Screen button, click this button to navigate to the next screen. This button is not active (that is, it is dimmed) until you click the Previous Screen button. Refresh Current Screen Click this button, shown in Figure 32, to refresh the current screen. User Home Screen Click this button, shown in Figure 32, to display the User Home Screen. The User Home Screen is the first screen displayed when you log in to Sentral and each time you click the User Home Screen button. The dashboard is the default home screen for all users. NOTE You can not set all Sentral screens to be the User Home Screen. To set a screen to be your home screen: 1. Ensure that the screen currently displayed is the screen that you want to be your home screen. 2. From the main menu, click Edit > Set current screen to home. 3. Click OK to confirm your selection. Sentral Administrator s Guide 71

84 Help Click the Help button, shown in Figure 32, to display the Sentral Help dialog box. Figure 33. ClearCube Sentral Help dialog box The Help dialog displays the version number of your Sentral installation and provides a link to the ClearCube Support Web site. Use the Support site to obtain updated documentation and software. Utilization Charts The Sentral dashboard, shown in Figure 28 on page 65, provides utilization charts that show: Network utilization over time Node parameters such as number of connections, processor utilization, memory utilization, and network bandwidth utilization. To display the dashboard from the main menu, click Management > Dashboard. Alternatively, click the User Home Screen button, described in Menu Buttons on page 71, to display the dashboard. The User Home Screen button is set to display the dashboard by default. If the User home Screen is set to display a different screen, it will not show the dashboard. The following list briefly describes each utilization chart. Shared Connections Displays the number of connected users on all hosts and VMs in Sentral. The Y axis (vertical) specifies the number of connections and the X axis (horizontal) displays hourly time increments that correspond to the Dashboard Scale (hrs) value you specify in the Setup > Configuration screen. 72 ClearCube Technology, Inc.

85 Chapter 3: Starting with Sentral Average Processor Utilization The Y axis (vertical) specifies the average CPU use, in percentage, for all of the hosts and VMs in Sentral. The X axis (horizontal) displays hourly time increments that correspond to the Dashboard Scale (hrs) value you specify in the Setup > Configuration screen. Average Memory Utilization The Y axis (vertical) specifies the average memory use, in percentage, for all hosts and VMs in Sentral. The X (horizontal) axis displays hourly time increments that correspond to the Dashboard Scale (hrs) value you specify in the Setup > Configuration screen. Average Network Bandwidth Utilization The Y axis (vertical) specifies the average network bandwidth use, in percentage, on all of the hosts and VMs in Sentral. The X axis (horizontal) displays hourly time increments that correspond to the Dashboard Scale (hrs) value you specify in the Setup > Configuration screen. You can configure the time axis (Hours Lapsed) in the Configuration screen (see Figure 41 on page 90), and the percentage axis by clicking and dragging inside a graph. You can configure the Dashboard Utilization Charts in the following ways: Configuring Dashboard Refresh Time 1. From the main menu, click Setup > Configuration. 2. Specify a value in the Dashboard Refresh Time (min) text box. The value must be an integer. 3. From the toolbar, click the Save icon. Click OK to dismiss the confirmation dialog box. Configuring the Dashboard Scale You can configure the dashboard scale in either of the following ways: From the dashboard OR From the Configuration screen From the Dashboard Click anywhere in a graph and drag vertically to change the Y axis, or drag horizontally to change the X axis. Sentral Administrator s Guide 73

86 From the Configuration Screen 1. From the main menu, click Setup > Configuration. 2. Specify a value in the Dashboard Scale (hrs) text box. The value must be an integer. 3. From the toolbar, click the Save icon. Click OK to dismiss the confirmation dialog box. Resetting Dashboard Scales to Default Values Click the Refresh button ( axes to their default values. ), located below the main menu, to reset the percentage View Menu The View menu is located in the top-right corner of the Sentral console. You can create customized views in Sentral that display a specified set of nodes. Figure 34. Sentral dashboard view menu See Managing Views on page 175 for more information about views. Finding Nodes, Groups, and Entities in Sentral The following sections describe how to search for objects in Sentral. 74 ClearCube Technology, Inc.

87 Chapter 3: Starting with Sentral Simple Search from Node Listings Many Sentral console screens display information about nodes in tables. You can search for nodes or for node parameters in any table. Successful search No match for search term (note red text) Figure 35. Performing a simple search from a table in a Sentral screen To search for an object by name or another attribute listed in a table, perform the following steps: 1. Click anywhere in the column in which you are searching. 2. Open the search dialog by typing any of the following from your keyboard: Press Ctrl-F OR Press Shift-Ctrl-F to perform a case-sensitive search OR Press the F3 key 3. Type the letters of the text for which you are searching. If there is a match, Sentral highlights the row that contains the match. If there is no match, the text in the search dialog box turns red. 4. Press Enter on your keyboard to jump to the highlighted name or to close the dialog box. Sentral Administrator s Guide 75

88 Advanced Search Advanced search enables you to search records by parameters such as host name, operating system, serial numbers, allocation status, and so on. The following figure shows the Search screen. Search Results Parameters User Can Add to Search Search Type Drop Down Box Parameters Currently Selected for Search Figure 36. Advanced Search To perform an advanced search, perform the following steps: 1. From the Sentral menu, click Edit > Advanced Search to display the Search screen. 2. Click the Search Type drop-down menu and select a node type for which to search. 76 ClearCube Technology, Inc.

89 Chapter 3: Starting with Sentral 3. Optionally, narrow your search by selecting one or multiple parameters in the Available Fields pane, and then click the Add ( ) arrow button to add the search parameter to the Selected Fields pane. To further refine your search, double-click a parameter in the selected fields pane to display a dialog box similar to the following figure. Enter a text string and select one of the following options: Starts With Ends With In b/w (a text string contained within the search parameter) Exact Match Click OK to close the dialog box. 4. Click the Search button located on the toolbar. Search Button Sentral Administrator s Guide 77

90 Sentral Dialog Boxes Sentral displays the following types of message dialog boxes: Success Confirmation Error Sentral can also display dialog boxes from the component applications Sentral uses. Table Configuration Sentral displays information about nodes and sets of nodes in tables, as shown in the following figure. Figure 37. Node data displayed in table format and Configure Table menu This section describes each item in the Configure Table screen and describes how to use the screen s interface. 78 ClearCube Technology, Inc.

91 Chapter 3: Starting with Sentral From the Configure Table screen, you can change the columns that are displayed in a table. The following figure shows the Configure Table screen. Save Cancel Set Defaults Selected Column Display Name Available Columns Add Remove Figure 38. The Configure Table screen The Configure Table screen contains the following columns and buttons: Available Columns This column lists all of the columns, or parameters, that a particular screen can display about a node. Selected Column This column identifies the columns that a particular table is currently displaying. Display Name This column identifies the label, or text, that is displayed as the column s title. You can modify the label for any column in a table by doubleclicking the parameter in the Selected Column or in the Display Name column. Add ( ) Click to move a column to the Selected Columns area. Any column in the Selected Columns area is displayed in the table. Remove ( ) Click to remove the selected column from the table and move the column to the Available Columns area. Any column in the Available Columns area is not shown in the table. Save ( ) Click to save the changes you have made to the table columns and column labels. Sentral Administrator s Guide 79

92 Cancel ( ) Click to remove any changes you have made to the table. Set Defaults ( ) Click to return the table display to the default settings. The following sections describe: How to choose the columns to display in a table See Choosing Columns to Display in a Table How to remove a column from a table See Removing a Column from a Table How to change the heading text of a column in a table See Changing a Column s Text Label on page 81 Choosing Columns to Display in a Table 1. From a console screen that displays node information in a table, right-click any column heading to display the Configure Table menu. 2. Select the Configure Table menu option to display the Configure Table screen. 3. From the Available Columns area, select the column you want to appear in the table. 4. Click Add ( ) to move the column to the Selected Column area. 5. Click Save ( ) and then click Yes. The column is now displayed in the table. Removing a Column from a Table 1. From a console screen that displays node information in a table, right-click any column heading to display the Configure Table menu. 2. Select the Configure Table menu option to display the Configure Table screen. 80 ClearCube Technology, Inc.

93 Chapter 3: Starting with Sentral 3. From the Selected Column area, select the name of the column that you want to remove from the table. In the following example, we are removing the column named Group from the table. 4. Click the Remove button ( ) to move the column to the Available Columns area (columns listed in the Available Columns area are not displayed in the table). 5. Click Save ( ) and then click Yes. The column is no longer displayed in the table. Changing a Column s Text Label You can modify the label for any column in a table by double-clicking the parameter in the Selected Column or in the Display Name column. Perform the following steps to change a column s label. 1. From a console screen that displays node information in a table, right-click any column heading. 2. Select the Configure Table menu option to display the Configure Table screen. 3. To change a column s label, the column must be a Selected Column. If the column you want to change is in the Available Columns area, select the column and click the Add button ( ) to move it to the Selected Column area. 4. Select the column whose label you want to change and double-click it. 5. Type a new name for the column and click OK. 6. Click Save ( ) and then click Yes. You can configure the tables displayed in the following screens. Management > Hosts Management > Thin Clients Management > Virtual Machines Sentral Administrator s Guide 81

94 Management > Groups Management > Users Health & Status > Alerts > View Deployed Alerts Reports > Inventory Reports > Alerts Reports > Equipment History 82 ClearCube Technology, Inc.

95 Chapter 4: Configuring the Sentral Console Sentral is built around the following major components: Sentral Console The foundation of ClearCube Sentral is the Sentral console, a interface for in depth management and reporting. Through the Sentral console, IT administrators can view device and session information, monitor performance of all systems, and remotely take control of hosts and user sessions. Administrators can use the innovative custom views feature to view objects by device type, geographical location, or business unit. Sentral also provides device health reporting with custom alert events that send notifications to the console or to third-party applications. Switching Module Administrators can use the Switching Module to switch users between hosts or to take hardware control of any host. For more information, see Chapter 8, Switching Module, on page 217 Connection Brokering Module With the Connection Brokering Module, users can log in from any location and always connect to their assigned sessions. This Sentral feature, called Follow Me, enables roaming users to reconnect to their existing sessions without having to restart applications or endure lengthy login processes. The Connection Brokering Module also enables clientless access to hosts from any Ethernet-based access device, laptop, or PC through a Web browser. For more information, see Chapter 7, Connection Brokering Module, on page 205, and Disconnect and the Sentral Follow Me Feature on page 263. Virtual Machine Module The Virtual Machine Module enables you to manage virtual machines running on Sentral managed hosts. For more information, see Managing Hosts on page 133 and Managing Virtual Machines on page 160. All software components are installed together. The license key determines which modules are activated. For more information about license keys, see License Requirements on page 3. 83

96 Starting the Sentral Console This section describes how to log in to Sentral console. To log in to Sentral console: 1. Click Start > All Programs > ClearCube Sentral > ClearCube Sentral Console > ClearCube Sentral Console to display the ClearCube Sentral Console Login screen. 2. Type your user name and password. 3. The Domain pull-down menu defaults to the domain or workgroup (depending on authentication settings) of the computer running the console. Select the domain or workgroup to log in to, as appropriate, and click Login. NOTE If you do not have Local Administrator or Domain Administrator privileges with the login you are using, select CCT User from the Domain pull-down menu and log in with the CCT User account. See Configuring the CCT User Account on page 87 for more information. If you experience connection issues when logging in: Restart Apache Tomcat service and attempt to log in again. See What to Do First on page 265 for more information. Consider disabling or reducing the number of Active Directories that Sentral searches at login time. For instructions about how to disable or specify the Active Directories that Sentral searches, see Limiting Sentral Interaction with Active Directory Groups on page 95 Use the Ping command or a utility to verify connectivity to your Sentral Primary and Secondary servers and to your Sentral database. 84 ClearCube Technology, Inc.

97 Chapter 4: Configuring the Sentral Console When the Primary server is not available, all Sentral consoles log in to the Secondary server if one is configured. If you log in to the Secondary server when the Primary server is active, any actions you perform occur on the Secondary server only. ClearCube recommends logging in to the Primary Server when resolving login issues. The first time that you log in to the console, Sentral displays the Console Configuration Wizard, as show in the following figure. Figure 39. Configuration Wizard See Table 6 on page 91 for a detailed description of each section and field that you can configure in the wizard. After you complete the Configuration Wizard, and after each successful login, the Sentral Welcome screen is displayed. The Welcome screen displays your license status. The Dashboard screen, shown in Figure 40 on page 86, is the screen displayed after closing the Welcome screen. The Dashboard provides the following graphical displays in the left-hand column: Connections Displays the number of active connections between thin clients to hosts, thin clients to VMs, Users to hosts, and Users to VMs. Average Processor Utilization Displays the average processor utilization for all hosts and VMs visible to the Console. Sentral Administrator s Guide 85

98 Average Memory Utilization Displays the average memory utilization for all hosts and VMs visible to the Console. Average Network Bandwidth Utilization Displays the average network utilization for all hosts visible to the Console. The time axis (Hours Lapsed) can be configured in the Console Configuration screen (see Figure 41 on page 90), and the percentage axis can be configured by clicking and dragging inside the graph. Select the Refresh button to reset the Percentage axes to their default value. Figure 40. Sentral Console Dashboard showing utilization charts, device alert status, defined devices, and dedicated connections The Dashboard provides these displays in the right-hand column: Device Alert Status Displays information and status for the different devices such as chassis, hosts, hosts, thin clients, and virtual machines. Clicking on the numbers in the either OK, WARNING, or ALERT columns takes you to the Health & Status screen for selected devices. 86 ClearCube Technology, Inc.

99 Chapter 4: Configuring the Sentral Console Defined Devices Displays the color code for device connections such as Defined (blue box), Active (green box), and Disconnected (yellow box). Connections Displays the dedicated and shared devices connection status in the graphs with different colors, which is described in the Defined Devices pane. Resources Displays the individual devices (Chassis, Hosts, Thin Clients, and Virtual Machines) connection information with a graph. For devices to be displayed in these graphs, they need to be in one of the groups such as Dedicated, Shared, or Spared (except chassis). Configuring the CCT User Account The CCT User is a default user configuration with view permissions to all the areas in Sentral, and execute permissions to a limited set of areas. This user cannot be deleted, and additional CCT User IDs cannot be created. The default username is Administrator and the default password is clearcube. The password fields are casesensitive. Use this account when logging into Sentral the first time, and your login account is not a Domain Admin or local Admin account. NOTE You should change the password on the CCT User account the first time you use it. You may also change the name of the account if you wish. The account names superuser and root are not recommended. After changing the CCT User, you may want to change permissions to block access to the Configure CCT User function. See Setting Up Security on page 97 for more information. If you change the CCT User s account name or password and then lose the name or password, you will need to reinstall Sentral to recover the account. NOTE The CCT User account should only be used for configuration tasks. Many other tasks, such as user discovery, are disabled for this account. Setting Global Configurations for Sentral From the Sentral Console, you can set global configurations for the major Sentral components. The following list details the major components you can configure. Configuration Server Configuration Alert Configuration Sentral Administrator s Guide 87

100 FTP Configuration Database Configuration Discovery Configuration System Configuration Dashboard Configuration Security Groups Configuration Miscellaneous/Other Configuration See Table 6 on page 91 for detailed information about each configuration area. You can configure the Sentral Console in the following ways: Using the Configuration Wizard, as shown in the following figure. In the Configuration screen, as shown in Figure 41 on page 90. Using either of these methods you can set global parameters for these components, which Sentral pushes out to each node in the environment. Optionally, you can customize the configuration for each node after pushing out global configurations. The following sections describe different methods Sentral provides to set global configurations. Using the Configuration Wizard Sentral displays the Configuration Wizard when you log in to Sentral for the first time. Additionally, you can run the wizard any time from the main menu by clicking Setup > Configuration. Perform the following steps to start the configuration wizard: 88 ClearCube Technology, Inc.

101 Chapter 4: Configuring the Sentral Console 1. From the main menu, click Edit > Configuration Wizard. 2. The table of contents on the left side of the wizard shows each configuration area. The configuration area you are currently in is shown in bold text. Table 6, Console Configuration Fields, on page 91 details each field in the wizard. The table provides a brief explanation about each field. Complete each field and click Next to continue to the next screen. 3. Click Finish after completing the Miscellaneous wizard screen, and then click OK to dismiss the confirmation dialog. You can run the Configuration Wizard at any time using any of the following options from the main menu: Click Edit > Configuration Wizard. Click Setup > Configuration and then click the Configuration Wizard button ( ). Using the Configuration Screen The Configuration screen contains all global configuration settings for Sentral nodes. After specifying settings in the Configuration screen, you can push these settings to nodes by running a discovery. Sentral pushes the configuration settings to all nodes on the subnet on which you run the discovery. Perform the following steps to specify configuration settings. Sentral Administrator s Guide 89

102 1. From the main menu, click Setup > Configuration to display the Configuration screen, shown in the following figure. Figure 41. Configuration screen 90 ClearCube Technology, Inc.

103 Chapter 4: Configuring the Sentral Console Table 6. Console Configuration Fields 2. Specify values appropriate for your environment in each field. The following table details each field in the Configuration screen. All console configuration fields are mandatory. Wizard Area Field Name Description Configuration Alert Sender This field lists the address inserted into the From field in the header when the Console sends Alert s. The default value is and should be changed to the address of the administrator on whose behalf s from the Console are sent. Group SMTP Server This field lists the addresses of the recipients of the Console s. The default value is and must be changed to a valid address or addresses. Multiple addresses can be specified using the comma as a separator. This field specifies the SMTP ( ) server for your Admin Sender. The default value is mail.yourdomain.com and must be changed to the name of your SMTP server for Alert s to function. Incorrectly formatted SMTP names can provide unexpected results. Enter a valid SMTP mail server name. Server Configuration Primary Server This field specifies the Primary Sentral Server. The default value is the name of Primary server that was specified when the Sentral Server was installed. If the Sentral Console is installed on the Primary Sentral Server machine, localhost is not an acceptable value. The Primary and Secondary Server fields can specify the same machine and can be changed at any time. ClearCube recommends using a static IP address. Alert Configuration Secondary Server Server Type Alert Evaluation Interval (min) Alert Firing Interval (hrs) This field specifies the Secondary Sentral Server. The default value is the name of Secondary server that was specified when the Sentral Server was installed. If the Secondary Sentral Console is installed on the Secondary Sentral Server machine, localhost is not an acceptable value. The Primary and Secondary Server fields can specify the same machine and can be changed at any time. ClearCube recommends using a static IP address. This pull-down menu specifies whether the local Sentral Server is the Primary or Secondary server. Choices include: Primary Secondary When the same system is specified for the Primary and Secondary servers, the default value is Secondary. This field specifies the time interval for evaluating an Alert. The default value is 30 minutes. A timer is started the first time an Alert is sent. When the time specified in this field elapses, the Alert is reevaluated. This field specifies the time interval after which an Alert is fired. The default value is 1 hour. Sentral Administrator s Guide 91

104 Table 6. Console Configuration Fields (continued) Wizard Area Field Name Description FTP Configuration TFTP Host IP This field specifies the IP address for the TFTP host, which is used to provide firmware updates for the RMM. The default value is and the value for this field must be an IP address, not a hostname. Database Configuration FTP Host FTP User FTP Password Database Server Name This field specifies the name of machine where the FTP Server is running. The FTP host is used for software, BIOS, and thin client updates. The default value is empty. ClearCube recommends using a static IP address. This field specifies the user name for the FTP server. The default value is Administrator. This field specifies the password for the FTP user. Asterisks are displayed in place of the characters entered. This field specifies the name of the database server machine. The default value is the name of database server that was specified when the Sentral Server was installed. Database User Name This field specifies the name of the database user. The default value is the name of database user that was specified when the Sentral Server was installed. Database User Password Database Type This field specifies the password for the database user. Asterisks are displayed in place of the characters entered. The default value is the password specified when the Sentral Server was installed. This pull-down menu specifies the SQL database type. Choices include: SQL Server MySQL The default value is the type of database specified when the Sentral Server was installed. 92 ClearCube Technology, Inc.

105 Chapter 4: Configuring the Sentral Console Table 6. Console Configuration Fields (continued) Wizard Area Field Name Description Discovery Configuration Thin Client Update Timeout (min) Host Update Timeout (min) Discovery Update Config Discovery User Preference Mapping User Type This field specifies the amount of time in which a poll must be received before the thin client is marked Offline. The default value is 10 minutes. This field specifies the amount of time in which a poll must be received before the host is marked Offline. The default value is 10 minutes. This pull-down menu specifies whether the Sentral Console uses the push Discovery function from the Sentral network nodes. Choices include: True False The default value is True. When True, the values of the Primary Server, Secondary Server, Host Poll Time, Alert Evaluation Time, and Alert Firing Time parameters are pushed to the host agent; and the values of the Primary Server, Secondary Server, and Thin client Poll Time parameters are pushed for the thin client agent when discovery takes place. This pull-down menu specifies which user discovery type takes preference. Choices include: Local Domain The default selection is Domain. Specifies the type of mapping to perform. Sentral Groups created and defined in Sentral. Windows Active Directory groups. Thin Client Health Update Interval (min) This field specifies the time after which a thin client reports back to the server with a heartbeat, in minutes. This value should be less than the Thin client Refresh Time. The default value is 5 minutes. System Configuration Dashboard Configuration Host Health Update Interval (min) System User Name System User Password Dashboard Refresh Time (min) Dashboard Scale (hrs) This field specifies the time after which a host or VM reports back to the server with a heartbeat, in minutes. This value should be less than the Host Refresh Time. The default value is 5 minutes. This field specifies the Administrator username of the local system where the Console is running. It is required for scheduling reports and other tasks. The default value is Administrator. This field specifies the password for the Administrator account of the Console machine. Asterisks are displayed in place of the characters entered. This field specifies how frequently the Dashboard is automatically refreshed. The default value is 1 minute. This field specifies the default value for the number of hours displayed on the x-axis for the CPU Average Utility and Memory Average Utility graphs. These values can be changed on the Dashboard, and revert to this default value when you change to a different screen. The default value is 5 hours. Sentral Administrator s Guide 93

106 Table 6. Console Configuration Fields (continued) Wizard Area Field Name Description Security Groups Configuration Local Security Groups This multi-select list box displays the Security Groups returned by the machine. Select multiple security groups by holding the Shift or Ctrl key during selection. On the user s next login, if the user is a member of multiple groups (as selected from the local security groups), a pull-down menu is displayed that asks the user to select the group to be used for that particular session. Domain Security Groups This multi-select list box displays the Domain Groups from the domain to which the machine belongs. Only Domain Admins is available when logged in on the local machine. Select multiple security groups by holding the Shift or Ctrl key during selection. Miscellaneous/Other Configuration Domain Type Logging Level Connection Preference Staggered Labels On the user s next login, if the user is a member of multiple groups (as selected in domain security groups), a pull-down menu is displayed that asks the user to select the group to be used for login. This pull-down menu provides the basis for user authentication. Choices include: AD (Active Directory) NT (NT 4) The default selection is AD. This pull-down menu specifies the level of logging maintained by Sentral. Choices include: Warning (exceptions and critical errors are logged) Debug (group and device manipulations are logged) None (events of all levels are logged are logged) The default selection is None. This pull-down menu specifies which object takes priority when a host connection occurs and an Allocation with a user and a thin client are both configured for the same host. Choices include: IPort User The default selection is IPort. This pull-down menu specifies how labels on the Switching screens are displayed. Choices include: Host C/Port Both None The default selection is Both. 3. From the toolbar, click Save ( ). 4. Stop and then restart the Apache Tomcat service. a. Click Start > All Programs > Apache Tomcat > Stop Tomcat. b. Click Start > All Programs > Apache Tomcat > Start Tomcat. 94 ClearCube Technology, Inc.

107 Chapter 4: Configuring the Sentral Console 5. Restart Sentral console: a. From the main menu, click File > Exit, and then click OK. b. Click Start > All Programs > ClearCube Sentral > ClearCube Sentral Console > ClearCube Sentral Console. Your changes are now applied. Global Configurations and Conditions Requiring a Console and Apache Tomcat Service Restart Restart Sentral Console and Apache Tomcat service in the following conditions: Whenever you modify the following fields in the Configuration screen: Database Server Name Database User Name Database User Password Database Type Whenever the IP address of the Sentral console or the Sentral server changes Limiting Sentral Interaction with Active Directory Groups By default, Sentral automatically populates the database with all Windows Active Directory (AD) groups on your network at login time. If there are a large number of Active Directory groups in your environment, this can be a lengthy process. If you typically work with a smaller set of Active Directory groups, you can: Disable AD group search at login Manually import specific AD groups Disabling Addition of AD Groups to Sentral Database 1. From the computer where Apache Tomcat is installed (typically where Sentral server is installed), use a text editor to open the following file: C:\Program Files\Apache Group\Tomcat 4.1\webapps\CMSServer\ WEB-INF\configuration\properties\ServerConfiguration.xml 2. Find the automatic.security.group.update line and change the value to false, as shown in the following line: Sentral Administrator s Guide 95

108 <entry key="automatic.security.group.update">false</entry> NOTE Changing the value of automatic.security.group.update to false prevents Sentral from performing any AD user and AD group related tasks until you manually import AD groups. Manually Adding AD Groups to Sentral To perform any tasks with AD users or AD groups after preventing the addition of AD groups to the Sentral database, you must manually add AD groups to Sentral. See Adding Local and Domain Security Groups to Sentral User Groups on page 174 for instructions about how to add AD groups to Sentral using Sentral console. Configuring SNMP Simple Network Management Protocol (SNMP) is a protocol that enables you to manage nodes on an IP network. SNMP allows sending alerts and other messages across your network, and can help network administrators manage network performance, find and solve network problems, and plan for network growth. You can set a global SNMP configuration for hosts in your environment from Sentral console. 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click the Configure SNMP button ( ) to display the SNMP Configuration screen. 3. Edit the following parameters as appropriate for your environment. Table 7. Console SNMP Configuration Fields Field Name Port Generic Trap Trap Receiver Specific Trap Description This field specifies the UDP port to which traps are sent. The default is 162, and should not be changed unless you open this port across the network to your trap receiver system, and configure the receiver to accept SNMP traps on this port. This field indicates that the trap is enterprise-specific. SNMP vendors and users define their own traps under the private-enterprise branch of the SMI object tree. The default value is 6. This field specifies the system that receives the SNMP traps sent. The default value is localhost, and should be changed to the hostname or the IP address of the trap receiver system. This field specifies the enterprise-specific trap number, and applies only when the Generic Trap is set to 6. To process this trap properly, the NMS has to decode the specific trap number that is part of the SNMP message. The default value is ClearCube Technology, Inc.

109 Chapter 4: Configuring the Sentral Console Table 7. Console SNMP Configuration Fields (continued) Field Name Community String OID Enterprise Type of Trap Format Trap Sender Description This field specifies the SNMP community name used in traps sent to this destination. The default value is public. This field specifies the Object ID (OID). The default value is This field specifies the object identifier that uniquely identifies the Enterprise ID in the MIB. The default value is This field specifies the type of trap format. The default value is String. This field specifies the system where the SNMP agent that sends trap notifications to the host and port that you specify. The default value is localhost, and should be changed to the hostname or the IP address of the trap sender system if it is different from this Sentral console. 4. From the toolbar, click the Save button ( ). Click OK, and then click OK again to dismiss the confirmation dialog boxes. 5. From the toolbar, click the Deploy SNMP Configuration ( ) button. Sentral displays the hosts to which you can deploy the SNMP configuration. 6. Select the host or hosts to receive SNMP deployment. 7. Right-click a selected host and select Deploy SNMP Configuration. Click OK to dismiss the confirmation screen. The SNMP configuration is deployed to the selected hosts. Setting Up Security ClearCube Sentral employs an extensible security model. The security model is fully integrated with Active Directory, enabling administrators can take advantage of their existing Active Directory group structures without having to replicate them within Sentral. The Sentral security model provides a four-tiered architecture, allowing for extensive configuration. The four tiers include: General Access Specifies which users can log in to Sentral. Advanced Access Specifies the GUI areas each administrator can access. Sentral Administrator s Guide 97

110 Function Authorization Specifies which functions each Sentral user can perform. Group Authorization In conjunction with Function Authorization, this specifies the groups of nodes on which administrators can perform functions. General Access Administrators who need to access the Sentral Console are required to enter a username and password. These credentials can either be form the local Windows user accounts, or from Active Directory, or from an NT Domain. When Sentral is installed, the administrator (or superuser) can configure access policies using any of these methods. By default, local and Domain Administrators have full access. Unless a configuration change is made, only users in the local Administrators group will be allowed to login. Advanced Access Sentral allows user groups with sufficient access to set up permissions so that the superuser can limit which areas of the graphical user interface each user can access. The major areas of the GUI are: Management Health and Status Reports Switching Connection Brokering Setup Run Discovery Function Authorization and Resource Permissions In the Advanced Security tools, a user with sufficient access can create a policy that determines which actions within each section that a user has rights to perform. So groups of administrators can login under different policies that dictate not only which areas of the GUI they can access, but what actions they can perform on those screens. 98 ClearCube Technology, Inc.

111 Chapter 4: Configuring the Sentral Console For example, an administrator group may have access to the Switching Module screens. This group may have rights to perform Spare Switching but not have rights to take administrative control of a host. Is Write and Is Execute Resource Permissions You can specify Is-write and Is-execute permissions for Sentral resource groups in the Advanced Security screen. Is-write and Is-execute resource permissions enable all users in specified group to perform various tasks within Sentral. NOTE When you apply a permission to a resource group, child groups do not inherit the permission. To assign permissions to subgroups or children of a parent resource group, you must explicitly apply permissions to each child group. The following list describes Is-write and Is-execute resource permissions. Is-write The permissions in this group correspond to tasks in which Sentral writes data. WriteConfig Allows users to write configuration settings from the console s Configuration screen. Group_Info_Manipulation Allows users to add groups, delete groups, and modify groups. Group_Node_Manipulation Allows users to add nodes, remove nodes, and delete nodes from a group using drag and drop operations. Mapping_Manipulation Allows users to perform all mapping tasks. Thin_Client_Update Allows users to update thin clients. Firmware_Update Allows users to update RMC firmware Host_Update Allows users to update host and host BIOS renamelcd Allows users to modify host LCD display resethost Allows users to reset, or cycle, host power Is-execute The permissions in this group correspond to tasks that Sentral executes. Manage Thin_Client_Switching Allows users to perform thin client switching Sparing HostSparing Allows users to perform blade sparing Sentral Administrator s Guide 99

112 8x8 Allows users to perform 8x8 switching adminview admincontrol adminkvm To display the Advanced Security screen, perform the following steps: 1. Form the main menu, click Setup > Security to display the Security screen. 2. Right-click an empty space in the upper portion of the screen and select Advanced Security, as shown in the following figure. 100 ClearCube Technology, Inc.

113 Chapter 4: Configuring the Sentral Console 3. Select the Is-write area and the Is-execute area to make selections. Is-write area Is-execute area See Specifying GUI Access on page 103 and Creating and Specifying Policies on page 104 for information about how to apply the permissions to resource groups. Group Authorization Using the Advanced Security tools, the superuser can create a policy that adds more granularity to the Function Authorization described above. In addition to determining what functions an administrator can access, a policy can be created to determine what groups of devices the administrator can access for these functions. For example, a group of administrators may have access to the Switching screens and may have rights to perform spare switching. A policy can be created that determines what groups of hosts on which the administrator can perform spare switching. Using the full complement of security layers, access to the Sentral console can be controlled, different levels of administrators can be given different levels of Sentral Administrator s Guide 101

114 privileges, and responsibilities can be divided among different departments by providing access to different groups of nodes. NOTE For all login accounts, security groups, and authentication methods other than the Sentral System User account (the Sentral administrator), security settings need to be explicitly configured to allow these users and groups to see functional areas within Sentral. Otherwise, these users will be unable to see these areas. Setting up a New Security Group Setting up an administrative group in Sentral requires the following steps: 1. Enable the group to log in to Sentral. 2. Specify which Sentral console screens the group can access. 3. Configure advanced security for the group, including creating policies that specify which functions each administrative group can perform. The following sections describe how to perform each of these steps. Enabling Login Before you can apply policies to a group, you must enable the group to log in to Sentral. 1. From the main menu, click Setup > Configuration. 2. Select the group or groups to enable to log in. Perform one of the following: For local security groups only (when using local authentication) From the Local Security Groups list box, select the group or groups to enable to log in to Sentral. 102 ClearCube Technology, Inc.

115 Chapter 4: Configuring the Sentral Console For Domain security groups only (when using Domain authentication) a. Specify the type of Domain you are enabling to log in by selecting AD (Active Directory) or NT from the Domain Type drop-down box. b. From the Domain Security Groups list box, select the group or groups to enable to log in to Sentral. Local Security Groups List Box Domain Security Groups List Box 3. From the toolbar, click Save ( ), and then click OK to dismiss the confirmation screen. Specifying GUI Access After enabling a group to log in to Sentral, specify which Sentral console screens the group can access. Perform the following steps. 1. From the main menu, click Setup > Security. 2. Right-click an empty space in the upper portion of the screen and select New Permission, as shown in the following figure. Sentral Administrator s Guide 103

116 3. Select a group from the Security Group drop-down menu. This list is prepopulated with the Active Directory or NT groups if you are using AD or NT. Otherwise, it is populated with local security groups. 4. Select the Sentral console areas that the specified group can access. A group is granted access to selected areas only. 5. From the toolbar, click Save ( ). Click Yes to continue, and then click OK to dismiss the confirmation screen. Creating and Specifying Policies After granting an administrative group access to Sentral console screens, you can create policies to specify: The tasks that users in the group can perform The node groups on which they can perform the tasks Perform the follow steps to configure group and functional authorization: 1. From the main menu, click Setup > Security. 104 ClearCube Technology, Inc.

117 Chapter 4: Configuring the Sentral Console 2. Right-click an empty space in the upper portion of the screen and select Advanced Security, as shown in the following figure. 3. From the Group list in the lower portion of the screen, select a group for which to specify permissions. Group List Resource Group List Is-write List Is-execute List Sentral Administrator s Guide 105

118 4. From the Resource Group list in the lower portion of the screen, select the resource group upon which the group can perform operations. NOTE The CCT group is the default superuser group, so selecting it applies to all groups the permissions that you specify in the following steps. 5. Specify operations that the group can perform. a. Activate the Is-Write list and the Is-Execute lists to choose options from them. To active a list, select the check box below the list title. b. Select any number of permissions from one list or from both lists. 6. From the toolbar, click Save ( ). Click Yes to continue, and then click OK to dismiss the confirmation screen. See Is Write and Is Execute Resource Permissions on page 99 for more information about the Is-Write and Is-Execute resource permissions. Configuring and Using the CCT User Sentral comes with an account named CCT User that allows you to log into Sentral in the event that your Active Directory or NT Domain Server are offline and no local authentication is enabled. The CCT User is a default user configuration with view permissions to all areas in Sentral, and execute permissions to a limited set of areas. This user can not be deleted, and additional CCT users can not be created. The default user name is Administrator and the default password is clearcube. The password fields are case-sensitive. This user name and password should be changed immediately after installation. To modify the CCT User password or user name, perform the following steps: 106 ClearCube Technology, Inc.

119 Chapter 4: Configuring the Sentral Console 1. From the main menu, select Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Configure CCT User ( ) to display the Configure CCT User screen. 3. To change the user name and password, enter the appropriate values in each field. 4. From the toolbar, click Save ( ). NOTE The CCT User account should only be used for configuration tasks. Many other tasks, such as user discovery, are disabled for this account. Updating the Console Sentral console updates are typically provided by ClearCube or by Authorized Service Providers. You can update the Console by placing the following files on the FTP server: Update file A.zip file that contains files required to update the Console. Update file names must use the format: upd_mmddyyyy_v.zip where: upd indicates that the file is an update file. mmddyyyy specifies the two-digit month, two-digit day, and four-digit year that the file is uploaded to the FTP server. v specifies the update file version. The version can be any integer greater than zero..zip is the file extension. Answer file A file that contains predefined answers to questions asked during an installation. Update files must use the format: ans_mmddyyyy_v.run where: ans specifies that the file is an answer file. mmddyyyy specifies the two-digit month, two-digit day, and four-digit year that the file is uploaded to the FTP server. v specifies the update file version. The version can be any integer greater than zero. Sentral Administrator s Guide 107

120 .run is the answer file extension. If you are provided with console update files, perform the following steps to update the console. 1. Place the update and answer files in the following directory on the Sentral FTP server: C:\Program Files\ClearCube Sentral\FTPServer\ConsoleUpdate 2. From the main menu, click Setup > Update Console. The first time a user logs in after you place update files on the FTP server, the following message is displayed: Updates are available for the system. Do you want to update now? After updating restart Sentral. 108 ClearCube Technology, Inc.

121 Chapter 5: Managing Sentral Nodes After configuring Sentral Console as described in Chapter 4 Configuring the Sentral Console on page 83, you can: Run a discovery to discover all of the nodes in your Sentral environment, or discover nodes by type. From the Sentral Console, you can discover nodes of the following type: Chassis, including management daisy chains Hosts, including virtual machines, ClearCube blades, and AMT enabled hosts Thin clients, including ClearCube I/Ports ClearCube C/Ports Users and user groups Local, domain, and Active Directory security groups See Discovering Sentral Nodes for more information. Optionally configure individual nodes or sets of nodes to override global configurations that Sentral pushes out through the Configuration Wizard Discovering Sentral Nodes To gain the full power of device management within Sentral, you must perform a discovery operation to discover nodes that Sentral manages. Running a discovery can enable the following: Configuration of Sentral nodes and users User discovery Viewing health and status of Sentral nodes, including hosts, thin clients, virtual machines, and chassis remote management modules (RMM)s. The Discovery menu options include: Discover Users 109

122 Modify AMT Global Account AMT Discovery V10L Discovery New Subnet Discover Selected Subnets Discover All Subnets Schedule Time Schedule Discovery New Subnet Modify Selected Subnet Delete Selected Subnet Specifying Subnets to Use For Node Discovery To set up a new subnet for discovery, perform the following steps: 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Run Discovery ( ) to display the Discovery screen. 3. Right-click an empty space in the upper portion of the screen and select New Subnet. 110 ClearCube Technology, Inc.

123 Chapter 5: Managing Sentral Nodes 4. In the Subnet area, specify values for all of the following. Table 8. Subnet Fields Field Name Subnet Name Start IP Address End IP Address Specifies the name of the subnet. Description Specifies the starting IP address for the subnet. Enter a Class B or Class C IP address. Specifies the ending IP address for the subnet. Enter a Class B or Class C IP address. The value of the final octet in this address must be 254 or less. 5. From the toolbar, click Save ( ). Sentral displays a confirmation dialog box and displays the new subnet in the upper portion of the screen. Click OK to dismiss the confirmation dialog box. Discover Selected Subnets To discover selected subnets, perform the following steps: 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Run Discovery ( ) to display the Discovery screen. 3. Select and then right-click an existing subnet in the upper portion of the screen. 4. Select Discover Selected Subnets from the right-click menu. Sentral displays the Discovery Discovered Devices screen, showing the discovered nodes. Discovered nodes are displayed in the Hierarchical view. Discover All Subnets To discover all subnets in your Sentral environment, perform the following steps: 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Run Discovery ( ) to display the Discovery screen. Sentral Administrator s Guide 111

124 3. Right-click an empty space in the upper portion of the screen and select Discover All Subnets. Sentral displays the Discovery Discovered Devices screen, showing the discovered nodes. Discovered nodes are also displayed in the Hierarchical view. Schedule Discovery To schedule a discovery, you must: Specify a time for the discovery to start and, optionally, specify an interval for repeating the discovery. Schedule the discovery Perform the following steps. 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Run Discovery ( ) to display the Discovery screen. 3. From the upper portion of the screen, select and then right-click the subnet upon which the discovery will run. 4. Select Schedule Time from the right-click menu. Sentral displays the Date Time Management screen. The current date and time is displayed in the Schedule Time and Recurrence portion of the screen. 5. Use the spin boxes to specify a date and starting time, in the future, to perform a discovery. 6. Select an interval at which to perform the discovery. 112 ClearCube Technology, Inc.

125 Chapter 5: Managing Sentral Nodes 7. From the toolbar, click Save ( ). Sentral displays the Discovery screen. 8. Select and then right-click the subnet on which you just scheduled the discovery. Select Schedule Discovery from the right-click menu, and then click OK to dismiss the confirmation dialog box. Modify Selected Subnet To modify a subnet, perform the following steps: 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Run Discovery ( ) to display the Discovery screen. 3. Select and then right-click an existing subnet in the upper portion of the screen. 4. Select Modify Selected Subnets from the right-click menu. Sentral displays the Subnet screen. 5. Change any subnet parameters, as described in Table 8 on page From the toolbar, click Save ( ), and then click OK to dismiss the confirmation dialog box. Delete Subnet from Sentral Console To delete a subnet from the Sentral console, perform the following steps: 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Run Discovery ( ) to display the Discovery screen. 3. Select and then right-click an existing subnet in the upper portion of the screen. 4. Select Delete Selected Subnet from the right-click menu. Click Yes, and then click OK to dismiss the confirmation dialog box. 5. From the toolbar, click Save ( ), and then click OK to dismiss the confirmation dialog box. Sentral Administrator s Guide 113

126 Discovering and Adding Users In Sentral, users are the users defined in your Windows user groups. ClearCube recommends discovering the users in your environment and placing them in logical groups. This requires: Discovering users Creating a group or groups for the users Populating groups with the discovered users The following sections describe how to perform each of these tasks. Specifying the User Type to Discover You can discover: Windows Domain group users Local workgroup users Specify the type of users to discover in the Discovery User Preference field, located in the Configuration screen. 1. From the main menu, click Setup > Configuration. 2. Verify your setting in the Discovery User Preference drop-down menu. You can not discover Domain and Local users at the same time. To change the discovery type, perform one of the following steps: To discover Domain groups, select Domain. OR To discover workgroup users, select Local. 3. Ensure that all of the following are set for Domain or Local authentication, according to the discovery preference you specified in the previous step: 114 ClearCube Technology, Inc.

127 Chapter 5: Managing Sentral Nodes Sentral console login Ensure Domain login type corresponds with the setting in the Discovery User Preference field in the Setup > Configuration screen. Domain Drop Down Menu Operating system login (see operating system documentation for more information) Apache Tomcat (see product documentation for more information) 4. Ensure that the following correspond to the discovery preference you specified in the previous step: You are logged in to a local workgroup or into a Domain group, as appropriate, on the computer running Sentral console You are logged in to a local workgroup or into a Domain group, as appropriate, in Sentral console Apache Tomcat authentication is set to local workgroup or to Domain, as appropriate 5. Click Save ( ). When you change the Discovery User Preference selection, Sentral displays the following dialog box: Select Yes to delete any existing users and node data from the database. The users are repopulated when you run discovery (as described in the following section), and the nodes on the selected section of your network (Local Workgroup or Sentral Administrator s Guide 115

128 Domain, but not both) are automatically repopulated. If you select No, your database can contain inaccurate information for the chosen authentication, such as duplicate user names. 6. Verify that you are logged into your computer and into Sentral with the correct authentication (that is, Domain or Local). If you change your system authentication, restart your computer. You can now continue to run a discovery to discover Windows users. Discovering Users Perform the following steps to discover users. 1. From the main menu, click Setup > Configuration to display the Configuration screen. 2. From the toolbar, click Run Discovery ( ) to display the Discovery screen. 3. Right-click an empty space in the upper portion of the screen and select Discover Users. 4. Sentral displays the Available Security Group(s) dialog box. Select the Windows security groups (Domain or local) in which to discover users. Shift or CTRL click to make multiple selections. To discover all security groups, click All. 5. Click Submit to run the discovery. Sentral displays the Discovered Users screen, which shows the discovered users. NOTE User discovery can take a long time if there are a large number of users in your environment. 116 ClearCube Technology, Inc.

129 Chapter 5: Managing Sentral Nodes Use the scroll bar on the right-hand side of the screen to view up to 100 users. If more than 100 users are displayed, you can: Select additional pages in the Page # drop-down box. Use the navigation buttons, located on the bottom edge of the console, to move to the first page of users, the last page of users, or to move forward or backwards one page at a time. You can now continue by adding the users you discovered to Sentral groups, as described in the following section. Adding Users to Sentral To use the Windows users that Sentral discovers, add the users to Sentral groups. Perform the following steps: 1. Ensure that you have discovered users as described in Specifying the User Type to Discover on page 114 and in Discovering Users on page From the Discovered Users screen, right-click anywhere in the screen and select Add User from the right-click menu. Sentral displays the Connection Brokering - User Groups (Add) screen. 3. In the upper portion of the screen, select a Windows security group from the Group Name area. NOTE Some groups might not display users in Users area in the lower-left portion of the screen. Only groups that are discovered in the Discover Users screen, as described in the previous step, display users. If you are working with a group that does not display users, ensure that the group contains users. If it does, discover the user group and continue to the next step. 4. From the Users area in the lower-left portion of the screen, select the users to add to a Sentral group. 5. From the Select Target Group area in the lower-right portion of the screen, select the Sentral group to add the users to. 6. From the toolbar, click Add ( ). Click OK to close the confirmation dialog box. You can now perform mapping and connection brokering tasks on the users you added to a Sentral group. The Sentral user group is now visible in the following console areas: Hierarchical view Management - Users screen Sentral Administrator s Guide 117

130 Connection Brokering - Groups screen Reports - Custom Reports screen Management Tasks The Management menu provides sets of tasks to manage the following: Chassis Hosts C/Ports Thin Clients Virtual Machines Users Views Groups The following table shows which of these menu items are displayed, depending on the Sentral modules activated on your system. Table 9. Management Menu Items Displayed by Module Management Menu Items C = Console D = Connection Brokering Module S = Switching Module V = Virtual Machine C C + D C + S C + D + S C + D + S + V Chassis X X X Hosts X X X X X C/Ports X X X Thin Clients X X X Virtual Machines X Users X X X Views X X X X X Managing Chassis In Sentral, you can manage ClearCube A series and R series chassis. You must discover the chassis in your environment to perform any chassis management tasks. 118 ClearCube Technology, Inc.

131 Chapter 5: Managing Sentral Nodes To navigate to the Chassis Management screen from the main menu: 1. Click Management > Chassis. 2. Select one of the following: R-Series Chassis OR A-Series Chassis From the Chassis Management screen, right click menus allow you to perform the following tasks: Configure a chassis View a chassis s health and status Update firmware for a chassis or for a chassis group Add RMC information Discover and view an Admin Daisy Chain Discover and view a Spare Daisy Chain Populate the host inventory for a chassis View equipment history for a chassis Run Chassis Discovery Run Chassis Discovery To run chassis discovery, perform the following steps: 1. From the main menu, click Management > Chassis, and then select one of the following: R-Series Chassis OR A-Series Chassis 2. Sentral displays the Chassis Management screen. Right click anywhere in the screen and select Run Discovery to display the Discovery screen. (The Discovery screen displays subnets that have been specified for discovery. For more information, see Specifying Subnets to Use For Node Discovery on page 110.) 3. Right click an any empty space in the screen and select Discover All Subnets. Sentral Administrator s Guide 119

132 OR Select and then right click a subnet, and click Discover Selected Subnet. Sentral displays the discovered chassis in the Discovery Discovered Devices screen. NOTE In this procedure, Sentral discovers and displays chassis only. To discover all nodes, click Setup > Configuration > Run Discovery. For more information, see Discovering Sentral Nodes on page 109. If you do not specify a hostname in the Location1 field of the Configure Chassis Management screen (see Table 10 for more information), Sentral displays an IP address to identify a ClearCube remote management module (RMM) in the Discovery - Discovered Devices screen. Configuring Chassis The following list describes the ClearCube chassis you can configure: R4300 chassis After discovering an R4300 chassis a chassis with a remote management module (RMM) installed you can configure it in Sentral. R4200 chassis You can configure R4200 chassis using Telnet. For more information about configuring RMCs and RMMs using Telnet, see the R Series Data Center Products User s Guide. To configure an R4300 chassis, perform the following steps: 1. From the main menu, click Management > Chassis > R-Series Chassis to display the Chassis Management screen. 2. From the list of chassis, select the row that identifies the chassis you want to configure. Look in the Model column to identify R4300 chassis. Model Column 120 ClearCube Technology, Inc.

133 Chapter 5: Managing Sentral Nodes 3. Right click the selected chassis and select Configure to display the Configure Chassis Management screen. NOTE Sentral displays an error message if you select an R4200 chassis. 4. Modify the parameters as described in the following table. Table 10. Chassis Configuration Fields Field Name IP Mode Description This pull-down menu specifies the IP Mode for the chassis. Choices include: DHCP Select if using DHCP to set your RMMs IP addresses. Static Select if configuring RMM IP addresses statically. The default selection is DHCP. RMM Port REQUIRED FIELD IP Address REQUIRED FIELD Gateway REQUIRED FIELD Only displayed for RMM Version 5.3 Build 2 and above. This field specifies the TCP/IP port for the RMM. The default value is 80. This field specifies the static IP address for the RMM. The default value is This field specifies the gateway IP address for the chassis. The default value is Community String This field specifies the Community string for SNMP. The default value is Public. Net Mask REQUIRED FIELD Log Server IP REQUIRED FIELD Alert Server IP REQUIRED FIELD Sentral Server Port REQUIRED FIELD Primary Server REQUIRED FIELD Secondary Server REQUIRED FIELD This field specifies the netmask for the RMM. The default value is Do not change this value unless using a netmask for other than Class C IP addresses on your network. This field specifies the IP address for the Log Server. The default value is This field specifies the IP address for the Alert Server. The default value is This read-only field specifies the TCP/IP port for the RMM. The default value is This field specifies the Primary Sentral Server. The Primary server is specified in the Console Configuration table, shown on Table 6 on page 91. The default value is This field specifies the Secondary Sentral Server. The Secondary server is specified in the Console Configuration table, shown on Table 6 on page 91. The default value is Alerting This pull-down menu specifies whether Alerting is enabled. Choices include: Enabled Alerting is enabled. Disabled Alerting is disabled. The default selection is Disabled. When Alerting is disabled, the pulldown menu for Alert Level is deactivated. Sentral Administrator s Guide 121

134 Table 10. Chassis Configuration Fields (continued) Alert Level Logging Log Level Telnet SSL SSH HTTP Field Name Timeout Value (min) Description This pull-down menu specifies the level of Alerting that is performed. Choices include: Low Errors only Medium Errors and Warnings High Errors, Warnings, and Notes The default selection is High. When Alerting is set to its default value of Disabled, this pull-down is deactivated. This pull-down menu specifies whether Logging is enabled. Choices include: Enabled Logging is enabled. Disabled Logging is disabled. The default selection is Disabled. When Logging is disabled, the pulldown menu for Log Level is deactivated. This pull-down menu specifies the level of Logging that is performed. Choices include: Low Errors only Medium Errors and Warnings High Errors, Warnings, and Notes The default selection is High. When Logging is set to its default value of Disabled, this pull-down is deactivated. This pull-down menu specifies whether Telnet is enabled. Choices include: Enabled Telnet is enabled. Disabled Telnet is disabled. The default selection is Enabled. This pull-down menu specifies whether SSL is enabled. Choices include: Enabled SSL is enabled. Disabled SSL is disabled. The default selection is Disabled. Note: All R4300 chassis on the same Admin chain must have SSL set the same. This pull-down menu specifies whether SSH is enabled. Choices include: Enabled SSH is enabled. Disabled SSH is disabled. The default selection is Disabled. Note: All R4300 chassis on the same Admin chain must have SSH set the same. This pull-down menu specifies whether HTTP is enabled. Choices include: Enabled HTTP is enabled. Disabled HTTP is disabled. The default selection is Enabled. This field specifies the timeout value in minutes for the RMC. The default value is 120. Note: This field is a read-only field. To configure this field, use telnet. 122 ClearCube Technology, Inc.

135 Chapter 5: Managing Sentral Nodes Table 10. Chassis Configuration Fields (continued) Field Name Password Location1 Location2 Description This field specifies the password for the RMM. The default value is clearcube. This value is shown as asterisks ( ********* ) in the Password text box. This field specifies the RMM hostname. The default value is empty. If this field is empty, RMMs appear in the console s Discovery - Discover Devices field with their IP address. This is a user-definable field. You can use this field to add any additional identifying information, such as the chassis physical location. The default value is empty. 5. From the toolbar, click Save ( ) to save you changes. It is recommended, but not required, to use identical chassis configurations (except for the actual IP address) across your network. For RMM failover to work, SSL and SSH settings must be identical for all chassis on a given Control chain. If notification of device discovery is activated (from the Configuration screen), the message specifies Sentral has discovered the following node(s): hostname --(nnn.nnn.nnn.nnn), RMM, where hostname is the hostname specified in the Location1 field in the Configure Chassis Management screen and nnn.nnn.nnn.nnn is the RMM IP address. If no hostname is specified, Sentral displays the RMM IP address in the Discovery - Discovered Device screen, and the contains the IP address in place of the hostname. Additional tasks in the Tasks menu include: Update Firmware (see Update Chassis Firmware on page 128 for this procedure) View Health and Status (see Health & Status Tasks on page 176 for more information) View Equipment History (see View Equipment History on page 131 for this procedure) Run Discovery (see Run Chassis Discovery on page 119 for this procedure) Add or Modify an RMC or RMM Perform the following steps to: Add an R series chassis RMC to the network, or to add an R series chassis RMM that is currently not connected to the network. Modify existing RMC or RMM information Sentral Administrator s Guide 123

136 1. From the main menu, select Management > Chassis > R-Series Chassis to display the Chassis Management screen. 2. Right click an empty space in the screen and select Add RMC information to display the RMC Information screen. 3. Select and then right click a chassis in the table. Perform either of the following: To add an RMC: Select Add RMC Information from the right-click menu. OR To modify RMC information: Select Modify RMC Information from the right-click menu. The fields in the lower portion of the screen become active (that is, they are no longer dimmed). Figure 42. Entering or modifying RMC Information 4. Add or modify information in the fields in the lower portion of the screen for each R4200 RMC on your network, and for each R4300 that is not currently connected to your network. NOTE Sentral does not check these fields for valid data. 124 ClearCube Technology, Inc.

137 Chapter 5: Managing Sentral Nodes The following table describes each field. Table 11. RMC Configuration Fields Field Name Chassis Group REQUIRED FIELD IP Address REQUIRED FIELD Password REQUIRED FIELD Port REQUIRED FIELD Model REQUIRED FIELD Description This field specifies the name of the Chassis Group. The default value is empty, and a name must be entered. This field accepts a maximum of 50 characters. This field specifies the static IP address for the RMC. The default value is empty, and an IP address must be entered. This field specifies the password for the RMC. The default value is empty, and a password must be entered. Port for RMC communication. The default value is empty. Enter 80. This pull-down menu specifies the type of RMC. Choices include: R4200 Select if configuring an RMC(R4200) R4300 Select if configuring an RMM (R4300) with a static IP address that is not connected to the network. The default selection is R From the toolbar, click Save ( ). NOTE When you add an RMM manually, you should perform a Discovery as soon as possible so that Sentral can correctly add all the data for the RMM into its database. In some cases when an RMM is added manually but not discovered, and it begins sending Logs and Alerts to Sentral, the data sent to Sentral may contain missing information. Delete an RMC or RMM Perform the following steps to delete RMCs and RMMs from your Sentral environment. NOTE If you do not disconnect or physically remove the RMM (R4300) that you delete with this procedure from your network, the RMM will be rediscovered by Sentral and repopulated in the database. 1. From the main menu, select Management > Chassis > R-Series Chassis to display the Chassis Management screen. 2. Right click an empty space in the screen and select Add RMC information to display the RMC Information screen. 3. Select and then right click a chassis in the table. Select Delete RMC information from the right click menu. 4. Click Yes, and then click OK to close the confirmation dialog boxes. Sentral Administrator s Guide 125

138 The RMC or RMM is removed from the list and from the Hierarchical view. Discover and View Daisy Chains The Admin and Spare Daisy Chains on R series chassis pass the digital link between the spare blade, the user s host, and the Admin C/Port in the same fashion that the digital link serves as the C/Port -to-dialog connection. The control link, an RS-485 signal, passes status and control information between the chassis. Thus, the actual control of the switching uses a separate channel from the dialog s signals. To have a complete path for control signals, the Control Chain is continuous throughout the Chassis Group, but multiple Admin and Spare Daisy Chains can be configured on one Control Chain. Figure 83 on page 286 shows an example of this. The Daisy Chain view provides a graphical representation of the physical cabling configuration of the Admin and Spare Daisy Chains. The Admin Daisy Chain view designates these connections in yellow, which corresponds to the recommended cabling color on the rear of the chassis. The Spare Daisy Chain view designates the connections in red, which corresponds to the recommended cabling color on the rear of the chassis. To discover and view a Daisy Chain, perform the following steps: 1. From the main menu, click Management > Chassis > R-Series Chassis to display the Chassis Management screen. 2. Select and then right click a chassis in the table. 3. Select one of the following: Discover Admin Daisy Chain OR Discover Spare Daisy Chain A graphic representation of the daisy chain for that chassis is displayed, as shown in Figure 43 on page After discovering the daisy chain, select and right-click the same chassis and select one of the following: View Admin Daisy Chain OR View Spare Daisy Chain 126 ClearCube Technology, Inc.

139 Chapter 5: Managing Sentral Nodes 5. Sentral displays a graphical representation of the daisy chain. Figure 43. Viewing an Admin Daisy Chain Screen NOTE If you select View Admin Daisy Chain before discovering the daisy chain, an error message is displayed. Always discover the daisy chain before viewing it. If you discover a daisy chain and move to another screen, you must rediscover the daisy chain to view it again. The view is not cached. Populate Host Inventory If a user deletes C/Ports from the Sentral console (visible in the Management > C/Ports screen), you can populate or repopulate the host inventory to restore the C/Ports in the Sentral console display. 1. From the main menu, click Management > Chassis > R-Series Chassis to display the Chassis Management screen. Sentral Administrator s Guide 127

140 2. Right click anywhere in the screen and select Populate Host Inventory. Sentral displays a confirmation dialog box when the host inventory is successfully repopulated. The process can take several minutes, depending on your environment, and the process can not be cancelled. Update Chassis Firmware This task updates the firmware only on the Primary chassis in a chassis group. If the chassis group has more than one R4300 RMM, then you need to update the entire chassis group. To update the entire chassis group, first update the Primary RMM with this procedure, then use the procedure found in Update Chassis Group Firmware on page 130 to finish updating the chassis group. Before updating chassis firmware, ensure that: The chassis is already discovered in Sentral. A TFTP Server is configured in the Configuration screen. The TFTP Server is running. To update a chassis s firmware, perform the following steps: 1. From the main menu, click Management > Chassis > R-Series Chassis to display the Chassis Management screen. 2. Right-click anywhere in the screen and select Update Firmware from the rightclick menu. Sentral displays the Selected RMMs screen. 3. Select and then right-click a chassis in the upper portion of the screen. Select Select for Update in the right click menu. 4. In the IP Address area in the lower left portion of the screen, Sentral displays the IP address of the primary RMM associated with the chassis. The Serial Number column is populated with the serial numbers of all chassis in this chassis's Admin chain. 5. From the Serial Number column, select the serial number of the chassis to update. 6. Click Browse and select the appropriate firmware file. 7. Update the chassis. Perform either one of the following steps: 128 ClearCube Technology, Inc.

141 Chapter 5: Managing Sentral Nodes From the toolbar, click Update Now ( ) to update the chassis immediately. OR a. From the toolbar, click Schedule Time ( ) to schedule a time to update the chassis. Sentral displays the Date Time Management screen. Figure 44. Scheduling a Chassis Firmware Update b. Select Once, and click the spin boxes to specify the date and time for the update to occur. Click the Save button. c. From the toolbar, click Update ( ) to set the scheduled update time. The following list describes other buttons in the Selected RMMs toolbar. Clicking Cancel ( ) in the Selected RMMs toolbar clears the IP Address column, the Serial Number column, and any path in the Firmware Update File text box. Clicking Remove ( ) removes any selected items from the IP Address column and the Serial Number column. The following is the sequence of events that occurs outside of Sentral: 1. Update within Sentral is started, either by Update Now or by the scheduled task. Sentral Administrator s Guide 129

142 2. The RMM firmware update file is copied to the TFTP Server. 3. The TFTP Server accepts the file and puts the file where it needs to go. 4. The TFTP Server sends out the update file to the RMM. 5. The RMM file updates. NOTE If the Sentral server is also the TFTP server, do not copy the firmware update file to the directory where the TFTP server is configured to retrieve the file. This will cause the update to silently fail. For example, if the RMM51b3 file in the directory C:\Firmware, do not configure the TFTP server to retrieve files from the same location. Update Chassis Group Firmware This task is necessary only when a chain of RMMs has been established in the hardware setup. Ensure that the Primary RMM in this chain has already been updated before performing this procedure. The following pre-existing conditions must be met: An R4300 chassis must be already discovered within Sentral. The Primary RMM of the Chassis Group must be loaded with the firmware that you wish to use to update the entire Chassis Group. A TFTP Server must be configured in Sentral's Configuration page. The TFTP Server must be running. To update a chassis firmware, perform the following steps: 1. From the main menu, click Management > Chassis > R-Series Chassis to display the Chassis Management screen. 2. Right-click anywhere in the screen and select Update Group Firmware from the right-click menu. Sentral displays the Selected RMMs screen. 3. Select and right click a chassis group from the upper portion of the screen. Select Select for Update from the right click menu. The IP Address list box in the 130 ClearCube Technology, Inc.

143 Chapter 5: Managing Sentral Nodes lower portion of the screen is populated with the IP addresses of the chassis group s Primary RMMs. 4. Click Browse and select the appropriate firmware file. 5. Update the chassis. Perform either one of the following steps: From the toolbar, click Update Now ( ) to update the chassis immediately. OR a. From the toolbar, click Schedule Time ( ) to schedule a time to update the chassis. Sentral displays the Date Time Management screen. b. Select Once, and click the spin boxes to specify the date and time for the update to occur. Click the Save button. c. From the toolbar, click Update ( ) to set the scheduled update time. NOTE If the Sentral server is also the TFTP server, do not load the firmware update file to the directory where the TFTP server is configured to get the file. This causes the update to silently fail. Additionally, the Primary RMM must be running the same version of the firmware update being sent to the Chassis Group, or the update will also silently fail. View Equipment History To view equipment history for a chassis, perform the following steps: 1. From the main menu, perform one of the following: For R-series chassis: Click Management > Chassis > R-Series Chassis. The Management Chassis screen is displayed. For A-series chassis: Click Management > Chassis > A-Series Chassis. Sentral displays the Chassis Management screen. Sentral Administrator s Guide 131

144 2. Select and then right-click a chassis row in the upper portion of the screen. From the right-click menu select View Equipment History to display the Chassis Management Equipment History screen. 3. Use right-click menus and toolbar icons to add, modify, or deleting equipment history reports. Use the lower portion of the screen to type reports. For more information, see View Health and Status of a Selected Chassis on page 177. NOTE The Equipment History field is limited to 3,000 characters. Configuring Host Connection Limits The following nodes can connect to hosts: Thin clients Users By default, Sentral allows only one connection to a host or virtual machine (VM) at a time. To permit multiple connections to a host or VM (that is, between a host and multiple thin clients or between a host and multiple users), you must modify the Sentral server configuration file. 1. Open the following file with a text editor: C:Program Files\ApacheGroup\Tomcat4.1\webapps\CMSServer\WEB-INF configuration\properties\serverconfiguration.xml 2. Search for the following line and change n to specify the number of simultaneous connections that a host permits. The value must be an integer, and the default value is 1: 132 ClearCube Technology, Inc.

145 Chapter 5: Managing Sentral Nodes <entry key="shared.connection.limit">n</entry> The value here specifies the number of permitted RDP sessions to a host. 3. Save and close the file. 4. Restart the Apache Tomcat service. Managing Hosts The right-click menu in the Management > Hosts > All Hosts screen enables you to: Configure a host View a host s health and status Map a host to a thin client Map a host to a user Update client software for a host or for a host group Update host BIOS Update host group BIOS Shut down or restart a host View equipment history for a host Run Host Discovery NOTE Some dual-nic hosts may display as an IP address for one of the two NICs. This is normal behavior, as the host is identified by the other NIC s IP address. Discovering Hosts To discover hosts in your environment, perform the following steps: 1. From the main menu, click Management > Hosts > All Hosts to display the Hosts Management screen. 2. Right-click anywhere in the screen and select Run Discovery to display the Discovery screen. Sentral displays existing subnets in the upper portion of the screen. If no subnets are displayed in the Subnet Name column, see Discovering Sentral Nodes on page 109 for information about how to discover subnets. 3. Perform either one of the following steps: Sentral Administrator s Guide 133

146 To discover hosts on all subnets: Right-click anywhere in the screen and select Discover All Subnets. OR To discover hosts on one subnet: Select and right-click a subnet. Select Discover Selected Subnets from the right-click menu. The Discovery Discovered Devices screen displays the discovered hosts on the subnet or subnets. NOTE With this procedure, Sentral returns only hosts discovered. To discover all nodes, use the Setup > Configuration> Run Discovery menu option from the main menu. For more information, see Discovering Sentral Nodes on page 109. Identifying ClearCube Blades in Sentral Console The following list shows ClearCube A1410 and R1350 PC blades and their corresponding serial number prefixes that are displayed in Sentral Console. A1410 AMAnnnnn R1350 ZRMnnnnn The Serial Number column, shown in Figure 46 and in Figure 47 on page 136, shows A-series and R-series serial numbers. Discovering Hosts with Dual (V5120) and Quad (V5140) Host Cards To discover a Dual or Quad host that contain a V5120 Dual Host card or a V5140 Quad Host card: 1. Perform a host discovery, as described in Discovering Hosts on page Perform a PCoIP discovery: a. From the main menu, click Management > All Hosts. b. Right-click anywhere in the screen and select Run Discovery. c. Select and then right-click a subnet that contains PCoIP hosts. Select PCoIP Device Discovery from the right-click menu (if no subnets are displayed in the Subnet Name column, see Discovering Sentral Nodes on page 109 for information about how to discover subnets). 134 ClearCube Technology, Inc.

147 Chapter 5: Managing Sentral Nodes Sentral displays the discovered hosts in the Discovery - Discovered Devices screen. If network congestion causes a lengthy discovery, Sentral displays the following message: Figure 45. Message indicating PCoIP discovery running in the background The PCoIP discovery continues running in the background, and you can continue to perform other tasks. Sentral displays discovered devices when the discovery is complete. Configure a Host To configure a host, perform the following steps: 1. From the main menu, select Management > Hosts > All Hosts. The Hosts Management screen is displayed, as shown in the following figure. Figure 46. The Hosts Management screen Sentral Administrator s Guide 135

148 2. Select and then right-click a host. Select Configure from the right-click menu to display the Configure Hosts Management screen, as shown in the following figure. Figure 47. Configure Hosts Management screen 3. Enter values for the parameters described in the following table. Table 12. Host Configuration Fields Field Name Timeout Value (min) Group REQUIRED FIELD Mapped To Asset Tag Stop Host Access Block Auto Config Primary Server REQUIRED FIELD Description This field specifies the timeout value in minutes for the host. The default is 10 minutes. This field specifies the name of the Chassis Group, and a name must be entered. The default is CCT\. This field accepts a maximum of 50 characters. This field specifies the user or thin client to whom the host is currently mapped. This is a user-definable field. The default value is empty. Allows halting access to this host. The default value is unselected. Allows blocking auto-configuration actions by the Sentral Console. The default value is unselected. This field specifies the Primary Sentral Server. The default value is empty. If Assign Server Values is selected, this field is filled with the name of the Primary server that is specified in the Console Configuration table, shown on Table 6 on page ClearCube Technology, Inc.

149 Table 12. Host Configuration Fields (continued) Field Name Chapter 5: Managing Sentral Nodes Description Secondary Server REQUIRED FIELD Poll Time (min) REQUIRED FIELD Alert Eval Time (min) REQUIRED FIELD Alert Firing Time (hr) REQUIRED FIELD This field specifies the Secondary Sentral Server. The default value is empty. If Assign Server Values is selected, this field is filled with the name of the Secondary server that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Host Poll Time, in minutes. The default value is 1. If the Assign Server Values checkbooks is checked, this field is filled with the Host Poll Time that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Alert Evaluation Interval, in minutes. The default value is 30. If the Assign Server Values checkbooks is checked, this field is filled with the Alert Evaluation Interval that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the time interval after which an Alert is fired. The default value is 1 hour. Assign Server Values When checked, the default values for the following fields are mapped from the Sentral Console to this host: Primary Server, Secondary Server, Poll Time (min), Alert Eval. Time (min), and Alert Firing Time (hr). The default value is unchecked. To use values other than those stored on the Console, uncheck this box. 4. From the toolbar, click Save ( ) and then click OK to close the confirmation dialog box. View a Host s Health and Status To view a host s health and status, perform the following steps: 1. From the main menu, click Management > Hosts > All Hosts. Sentral displays the Hosts Management screen. 2. Right-click anywhere in the screen and select Configure. The Configure Hosts Management screen is displayed. 3. Select a host from the upper portion of the screen. Host information is displayed in the lower portion of the screen. 4. From the toolbar, click View Health & Status ( ) to display the Health and Status Hosts screen. The upper portion of the screen and the tabs in the lower portion of the screen display a variety of health and status information. This screen is also available from the main menu by clicking Health and Status > Hosts. Sentral Administrator s Guide 137

150 Map a Host to a Thin Client To map a host to a thin client, perform the following steps: 1. From the main menu, click Management > Hosts > All Hosts to display the Hosts Management screen. 2. Right-click anywhere in the screen and select Map Host to Thin Client. The Connection Brokering Mappings screen is displayed. 3. See the complete procedure in Dedicated Mappings (Thin Clients to Hosts) on page 207. Map a Host to a User To map a host to a user, perform the following steps: 1. From the main menu, click Management > Hosts > All Hosts to display the Hosts Management screen. 2. Right-click anywhere in the screen and select Map Host to User. The Connection Brokering Mappings screen is displayed. 3. See the complete procedure in Dedicated Mappings (Users to Hosts) on page 209. Update Client Software for a Host or Host Group To update the Sentral host agent software for a host or a host group, perform the following steps: 1. Ensure that you have an update file and an answer file for your host or host group. 2. From the main menu, click Management > Hosts > All Hosts to display the Hosts Management screen. 3. Right-click anywhere in the screen and select Update Host Agent (or Update Host Agent Group) to display the Update Host Agent Management screen. The screen displays discovered hosts. 4. Select and right-click one or more hosts. Select New Update from the right-click menu. Sentral displays the selected hosts in the list box located in the Selected Host portion of the screen. 5. Click the Update File Browse button to navigate to the appropriate update file. Select the file and click Open. Sentral ignores any characters you type in this text box. 6. Click the Answer File Browse button to navigate to the appropriate answer file. Select the file and click Open. Sentral ignores any characters you type in this text box. 138 ClearCube Technology, Inc.

151 Chapter 5: Managing Sentral Nodes 7. From the toolbar, click Schedule Time ( ) to display the Date Time Management screen. 8. Click the spin boxes to specify the date and time for the update to occur, and then select an interval to specify how often the update should occur. 9. From the toolbar, click the Save button. 10. From the toolbar, click Update ( ) to set the update to run at the scheduled time. The Update and Answer files are copied to the Sentral update cache. At the designated time, Sentral performs the update. NOTE The Update Host Agent screen provides a button marked Select by Group. Click this to update all the clients in one or more host groups. Clicking this button brings up the same screen as clicking the Update Host Agent Group button. NOTE The Update Host Agent Group screen provides a button marked Select by Host. Click this button to select individual hosts instead of host groups. Clicking this button brings up the same screen as clicking the Update Host Agent button. Update a Host BIOS or Host Group BIOS To update the BIOS on a host or host group, perform the following steps: 1. From the main menu, click Management > Hosts > All Hosts to display the Hosts Management screen. 2. Right-click anywhere in the screen and select Update Host BIOS (or Update Host Group BIOS) to display the Update Host BIOS Management screen (or Update Host Group BIOS Management screen). The screens display discovered hosts and host groups. Sentral Administrator s Guide 139

152 3. From the upper portion of the screen, select the host or host group containing the BIOS requiring an update. Toolbar Host Parameters Figure 48. Management Update Host BIOS Screen 4. In the host parameters fields above the toolbar, Enter valid information in the User Name, Password, Domain, and Select Drive fields. In the Host Group BIOS screen only, select the correct host type. 5. In the upper portion of the screen select and then right-click one host or host group, and then select New Update. The host or host group is displayed in the Host Name and IP Address list boxes in the lower portion of the screen. 6. Perform either of the following: From the toolbar, click Update Now ( ) to immediately update the host or host group BIOS. OR From the toolbar, click Schedule Time ( ) to schedule the BIOS update time. After scheduling the time, click Update ( ). 140 ClearCube Technology, Inc.

153 Chapter 5: Managing Sentral Nodes Flow of Files 1. Sentral uploads the BIOS files to the FTP Server (configured in Sentral's Setup > Configuration page). 2. The FTP Server sends files to the Host's X:\ccbiosflash drive, where X is the hard disk that you specify. 3. The host displays a popup window stating that Windows is restarting and any unsaved work will be lost (gives 30-second countdown). 4. The host restarts. 5. Re-login occurs (this happens from a script that is automatically run), using the data that was entered on the Management > Update Host BIOS screen. 6. A window is displayed with warning that the user should not disrupt the BIOS update process. Notes BIOS update does not work to update R1100 blades. No error message is sent if the username, password, or domain is incorrect. If an incorrect WPH file is uploaded to the host, the host will not update. The user receives no confirmation whether the BIOS update was successful. The message Please make sure following systems(s) are not locked for restart. is displayed for all systems running Windows 2003 Server R2 Standard Edition. This operating system allows locking to prevent unauthorized restarts. If you are updating the BIOS on a system running Windows 2003 Server, ensure that the system is unlocked before you perform the update, so the BIOS update can take place. If the system is locked, the BIOS update will silently fail. Shut Down or Restart a Host To shut down or restart a host, perform the following steps: 1. From the main menu, click Management > Hosts > All Hosts to display the Hosts Management screen. 2. Select and then right-click a host. Select Restart Host or Shutdown Host. Click Yes to confirm the action, and then click OK to close the confirmation dialog box. If a user is logged in to the host, a dialog box indicates that a shutdown is in progress. Sentral Administrator s Guide 141

154 You can shut down and restart hosts with AMT using their right-click menus. See Using a Host s AMT Features on page 143 for more information about these and other options. View Equipment History for a Host To view equipment history for a host, perform the following steps: 1. From the main menu, click Management > Hosts > All Hosts to display the Hosts Management screen. Select a host from the table in the upper portion of the screen. 2. Right-click the host and select View Equipment History. From this screen you can add, modify, or delete equipment history reports. For more information, see View Health and Status of a Selected Host on page 182. NOTE The Equipment History field is limited to 3,000 characters. Managing PCoIP Hosts The following figure shows PCoIP hosts (R1350 or A1410 blades) in the Management - PCoIP Hosts screen. Figure 49. PCoIP hosts and details about the PCoIP cards (V5120 Dual Host cards) they contain The screen shows PCoIP hosts and provides details about the hosts and the PCoIP hosts (that is, V5120 Dual Host cards) they contain. The following list details each column in the Management - PCoIP Hosts screen: Hostname Hostname of the host IP Address IP address of the host MAC Address MAC address of the host PCoIP Host MAC Address MAC address of the V5120 Dual Host card Host Card IP Address IP address of the V5120 Dual Host card 142 ClearCube Technology, Inc.

155 Chapter 5: Managing Sentral Nodes Managing PCoIP Hosts (V5120 Dual Host Cards) You can configure PCoIP hosts, or V5120 Dual Host cards, individually or in sets. When configuring V5120 Dual Host cards, you can specify the card s: Primary server Poll time Configuring One V5120 Dual Host Card Perform the following steps: 1. From the main menu, click Management > Hosts > PCoIP Hosts. 2. Select and then right-click a host. Select either of the following: Configure PCoIP Host to configure a single host. Configure Multiple PCoIP Hosts to configure two or more hosts to use the same server and poll time. Sentral displays the corresponding Configure PCoIP Host screen. 3. From the upper portion of the screen, select a host. From the Configure Multiple PCoIP Hosts screen only, use CTRL+click or SHIFT+click to select multiple hosts. 4. Sentral retrieves information from the selected host or hosts V5120 Dual Host cards and displays the host (V5120 Dual Host card) properties in the text boxes in the lower portion of the screen. 5. Specify a new value in the Primary Server text box, the Poll Time (min) text box, or both. 6. From the toolbar, click Save ( ) to save your changes. Using a Host s AMT Features You can use Intel Active Management Technology (AMT) features on certain A series hosts to manage the hosts out-of-band. AMT enables hardware-level access to a host if it is inserted in a chassis and connected to an Ethernet network. AMT-level communication occurs independent of any operating system state; that is, the host must be connected to power but it does not have to be powered on to perform AMT tasks. NOTE You must enable AMT in a host before you can use AMT features. See A1410 Quick Start Guide for information about configuring hosts for outof-band management. Documentation is available at Sentral Administrator s Guide 143

156 You can perform the following tasks on AMT hosts in Sentral: Set AMT Administrator see Set AMT Administrator on page 144 for more information. Configure AMT Management see Configure AMT Management on page 145 for more information. AMT Power On see AMT Power On on page 146 for more information. AMT Shutdown Host see AMT Shutdown Host on page 146 for more information. AMT Restart Host see AMT Restart Host on page 146 for more information. AMT Console Redirect see AMT Console Redirect on page 146 for more information. Before you can use Sentral to perform AMT tasks, you must provision AMT on each host in your Sentral environment. See Provisioning AMT on Hosts on page 199 for more information. To access AMT-specific features of a host in Sentral you can: Right-click the AMT icon in the hierarchical view. See Hierarchical View Icons on page 68 to see the AMT icons. OR From the main menu, click Management > Hosts > PCoIP Hosts. Set AMT Administrator To perform AMT tasks on a host you must specify an AMT administrator. Only the administrator that you specify in this screen can perform AMT tasks on the host. This administrator is not the same as the Sentral administrator. To set an AMT administrator from the Hierarchical view: 1. From the Hierarchical view, right-click an AMT enabled host icon and select Set AMT Administrator to display the Configure AMT Hosts Management screen. 2. Type the AMT administrator's user name and password. All characters are allowed. 3. From the toolbar, click Save to set the AMT administrator. Deleting Credentials on AMT Host To delete AMT credentials, perform the following steps: 144 ClearCube Technology, Inc.

157 Chapter 5: Managing Sentral Nodes 1. From the main menu, click Management > Hosts > AMT Hosts. 2. Select and right-click an AMT enabled host, and select Set AMT Administrator. 3. Provide the AMT administrator's user name and password, and select the Delete Credentials option. 4. From the toolbar, click Save to delete the user name and password on the selected AMT enabled host. When the credentials are deleted, Sentral uses the global password to access the device. Configure AMT Management This option enables you to use an AMT Web page, located on the host, to access AMT features that are not available through Sentral. To access these advanced features from the Hierarchical view: 1. From the Hierarchical view, right-click an AMT enabled host icon and select Configure AMT Management to display the Log On screen. Click Log On to display the Enter Network Password dialog box. NOTE You must specify an AMT administrator and password, as described in Set AMT Administrator on page 144, before you can log in. 2. Type your AMT administrator name and password in the appropriate text boxes and then click OK to open AMT Web page. Figure 50. AMT options Sentral Administrator s Guide 145

158 For more information about these AMT features, see Intel Active Management Technology with System Defense Feature Quick Start Guide, part number D (d pdf) on the Intel support site. AMT Power On To power on an AMT enabled host from Sentral, perform the following steps from the Hierarchical view. 1. From the Hierarchical view, right-click an AMT enabled host icon and select AMT Power On. 2. Click Yes to continue, and then click OK to close the confirmation dialog box. AMT Shutdown Host To shut down an AMT enabled host from Sentral, perform the following steps from the Hierarchical view. 1. Right-click an AMT enabled host icon and select AMT Shutdown Host. 2. Click Yes to continue, and then click OK to close the confirmation dialog box. AMT Restart Host To restart an AMT enabled host from Sentral, perform the following steps from the Hierarchical view. 1. From the Hierarchical view, right-click an AMT enabled host icon and select AMT Restart Host. 2. Click Yes to continue, and then click OK to close the confirmation dialog box. AMT Console Redirect Use the console redirect option to redirect the video output from an AMT enabled host to the Sentral console you are currently using. You can this option, for example, if you need to: Access a host s BIOS Perform tasks on the host Install operating system images using a PXE server Follow the on screen instructions to perform any of these tasks. To redirect a selected host s video output to your Sentral console, perform the following steps from the Hierarchical view. 146 ClearCube Technology, Inc.

159 Chapter 5: Managing Sentral Nodes 1. From the Hierarchical view, right-click an AMT enabled host icon and select AMT Console Redirect. 2. Click Yes to continue, and then click OK to close the confirmation dialog box. 3. Press F10 to exit and return to your Sentral console. NOTE When you press the F10 button during console redirection, changes you make in the session are not saved. Windows Vista does not support console redirection. Advanced PCoIP Configuration To perform advanced PCoIP configurations: 1. From the Hierarchical view, select and then right-click a PCoIP host. 2. Select Advanced PCoIP Configuration to open the PCoIP login screen in a Web browser. 3. Type your PCoIP administrator password in the text box and click Log In. Managing C/Ports The C/Ports sub-menu allows you to perform the following tasks for C/Ports: Modify a C/Port Delete a C/Port View equipment history for a C/Port In the C/Ports Management screen, if Sentral displays a the value -1 in a C/Port Slot column, this indicates that this C/Port has been switched to the Spare Blade port or to the Admin Port on the chassis. See Chapter 8, Switching Module, on page 217 for more information on Spare and Admin switching. Modify a C/Port To modify a C/Port, perform the following steps: 1. From the main menu, select Management > C/Ports. Sentral displays the C/Ports Management screen, listing discovered C/Ports. 2. Select and right-click a C/Port. Select Modify from the right-click menu to display the Modify C/Port dialog box. 3. Change any of the following: Sentral Administrator s Guide 147

160 C/Port alias Chassis alias for the chassis to which the C/Port is connected 4. Click OK to save your changes, and then click OK to close the confirmation dialog box. Delete a C/Port To delete a C/Port from the database, perform the following steps: 1. From the main menu, click Management > C/Ports. Sentral displays the C/Ports Management screen, listing discovered C/Ports. 2. Select and right-click a C/Port. Select Delete from the right-click menu. 3. Click Yes to delete the C/Port, and click OK to close the confirmation dialog box. When you delete a C/Port, you remove its alias and its equipment history from the Sentral database. The next time you discover users, the C/Port s default name (C/Port n, where n is the chassis slot number for the C/Port) is restored. View Equipment History for a C/Port To view the equipment history for a C/Port, perform the following steps: 1. From the main menu, select Management > C/Ports. 2. Select and right-click a C/Port. Select View Equipment History in the rightclick menu to display the C/Ports Management Equipment History screen. 3. Select and right-click an entry in the upper portion of the screen. Make a selection in the right-click menu to add, modify, or delete equipment history reports. NOTE The Equipment History field is limited to 3,000 characters. Managing Thin Clients This section describes how to mange thin clients in your Sentral environment. The Thin Clients Management screen enables you to perform the following tasks for thin clients: Configure a thin client Configure multiple thin clients Create a global configuration for all Wyse V10L thin clients in your environment 148 ClearCube Technology, Inc.

161 Chapter 5: Managing Sentral Nodes View a thin client s health and status Map a thin client to a host Map a thin client to a VM Update client software for a thin client or for a thin client group View equipment history for a thin client Discover thin clients Figure 51 on page 149 shows the Thin Clients Management screen. Identifying Thin Clients without Operating Systems in Sentral In Sentral, the thin client management screens contain a hostname column, enabling you to identify thin clients by their hostname. Thin clients that do not run operating systems (such as ClearCube I94xx I/Ports and Wyse V10L thin clients) display their IP address in the hostname column, as sown in the following figure. Figure 51. Identifying thin clients in Sentral Discovering Thin Clients Perform the following steps to discover thin clients on the subnets in your Sentral environment. Sentral Administrator s Guide 149

162 1. From the main menu, click Management > Thin Clients to display the Thin Clients Management screen. 2. Right-click anywhere in the screen and select Run Discovery to display the Discovery screen. Sentral displays existing subnets in the upper portion of the screen. If no subnets are displayed in the Subnet Name column, see Discovering Sentral Nodes on page 109 for information about how to discover subnets in Sentral. 3. Perform either of the following to start the discovery: To discover thin clients on all subnets: Right-click anywhere in the screen and select Discover All Subnets. OR To discover thin clients on a selected subnet: Select one or multiple subnets and right-click your selection. Select Discover Selected Subnets from the right-click menu. Sentral displays the Discovery Discovered Devices screen showing all discovered thin clients. NOTE With this procedure, Sentral returns only thin clients discovered. To discover all nodes, use the Setup > Configuration> Run Discovery menu option from the main menu. For more information, see Discovering Sentral Nodes on page 109. Discovering I9420 and I9440 I/Ports I9420 I/Ports and I9440 I/Ports use PCoIP technology. Discovering I94xx I/Ports is similar to discovering other thin clients, but you must specifically discover PCoIP devices when running a discovery on a selected subnet. Perform the following steps to discover I94xx I/Ports: 1. From the main menu, click Management > Thin Clients to display the Thin Clients Management screen. 2. Right-click anywhere in the screen and select Run Discovery to display the Discovery screen. Sentral displays existing subnets in the upper portion of the screen. If no subnets are displayed in the Subnet Name column, see Discovering Sentral Nodes on page 109 for information about how to discover subnets in Sentral. 3. Select one or multiple subnets that contain PCoIP thin clients and right-click your selection. Select PCoIP Device Discovery from the right-click menu. 150 ClearCube Technology, Inc.

163 Chapter 5: Managing Sentral Nodes Sentral displays the Discovery Discovered Devices screen showing all discovered PCoIP thin clients. If network congestion causes a lengthy discovery, Sentral displays the following message: Figure 52. Message indicating PCoIP discovery running in the background The PCoIP discovery continues running in the background, and you can continue to perform other tasks. Sentral displays discovered devices when the discovery is complete. Configuring XPe Thin Clients Perform the following steps to configure thin client or multiple thin clients. 1. Ensure that your have discovered the XPe thin clients in your environment (you can discover all thin clients and select an XPe thin client to configure, or you can restrict discovery to V10Ls on a particular subnet). 2. Right-click a thin client in the Hierarchical view and select Configure to open the Configure Thin Client Management screen (to perform an action on multiple thin clients, ensure that you have selected thin clients of the same type). 3. In the lower portion of the screen, enter values or select options for the thin client or thin clients as detailed in Table 13 on page 152. Sentral Administrator s Guide 151

164 4. From the toolbar, click Save ( ) to save your changes, or click Cancel ( ) to discard your changes. Table 13. Thin Client Configuration Fields Field Name Timeout Value (min) Group REQUIRED Mapped To Asset Tag User Name Domain Name Color Max Time Server Port Description This field specifies the timeout value in minutes for the thin client. The default is 10 minutes. This field specifies the name of the thin client Group, and a name must be entered. The default is CCT\. This field accepts a maximum of 50 characters. This field specifies the host or VM to whom the host is currently mapped. This is a user-definable field. The default value is empty. Name of user to log in. You can specify a user name for a single thin client only, not for multiple thin clients. Name of Domain to log in to. You can specify a Domain name for a single thin client, not for multiple thin clients. This is the color quality right inputs 8 bit, 16 bit, 24 bit Time after which auto reconnect will occur right inputs positive numeric value (2,3 etc) Port number for server. Cache Bit Map This is the setting for Bitmap Caching right inputs True, False 152 ClearCube Technology, Inc.

165 Chapter 5: Managing Sentral Nodes Table 13. Thin Client Configuration Fields (continued) Override Host Name Connection Bar Auto Password Auto Connect Retry Last Host Enable Reboot Disable Close Redirect Devices Forward Drives Primary Server REQUIRED Secondary Server REQUIRED Poll Time (min) REQUIRED Host Name Password Field Name Allows overriding the default target host name during login. The default value is unselected. Whether to show the connection bar or not in case of full screen. True/False Whether to pass the password in case of Auto Login or not. True/False Whether to reconnect after disconnection or not. True/False True/False. Whether to save the last host connected or request new host from server for connection retrying. Whether to show the Reboot button on thin client GUI or not. True/False Whether to allow closing of thin client agent window or not. True/False Whether to redirect local devices during thin client agent session or not. True/False. NOTE: To disable the use of USB devices (including mass storage drives) on the thin client, ensure the Redirect Devices option and the Forward Drives options are both selected. Whether to redirect local drives during thin client agent session or not. True/False. NOTE: To disable the use of USB devices (including mass storage drives) on the thin client, ensure the Redirect Devices option and the Forward Drives options are both selected. This field specifies the Primary Sentral Server. The default value is empty. If Assign Server Values is selected, this field is filled with the name of the Primary server that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Secondary Sentral Server. The default value is empty. If Assign Server Values is selected, this field is filled with the name of the Secondary server that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Host Poll Time, in minutes. The default value is 1. If Assign Server Values is selected, this field is filled with the Host Poll Time that is specified in the Console Configuration table, shown on Table 6 on page 91. Name of Host to log in to. This is the Password Value Description Sentral Administrator s Guide 153

166 Table 13. Thin Client Configuration Fields (continued) Field Name Resolution Startup Time Max Retries Poll Status Assign Server Values Description This is the screen resolution. Applicable resolutions depend on OS and hardware. Possible values include 320x200, 320x240, 384x512, 400x300, 480x640, 512x384, 600x600, 640x480, 768x1024, 800x600, 1024x768, 1152x864, 1280x1024. How many minutes to wait before bringing up the Login window of thin client. Positive numeric value Number of retries for auto reconnect. right inputs positive numeric value Whether or not to poll in case of Connect/Disconnect from thin client agent (True/False). If set to false connect/disconnect information will be sent with the next push poll. This checkbox allows assigning the values stored on the Sentral Console for the Primary Server, Secondary Server, and Poll Time fields. The default value is unchecked. Stop Thin Client Config Allows halting reconfiguration of this thin client during an autodiscovery. The default value is unselected. Auto Login Auto Domain Enable Shutdown Edit Domain Forward Printers Forward Serial Ports Forward SmartCard Enable User Message Allow Mass Storage Sentral Mode Direct Mode Whether to auto login or not at thin client agent startup only. For connecting after disconnect use Auto Connect. True/False Whether to pass the domain in case of Auto Login or not. True/ False Whether to show the Shutdown button on thin client GUI or not. True/False Allow the user to edit the domain or not. True/False Whether to forward the printers information during the thin client agent session. True/False Whether to forward ports during thin client agent session or not. True/False Whether to forward SmartCard information during thin client agent session or not. True/False Whether to show user message after disconnection or not. True/False (This option is only displayed in I94xx I/Port configuration screens.) Select this option to allow users to use USB mass storage devices on I94xx I/Ports. (This option is only displayed in I94xx I/Port configuration screens.) Select this option to send I/Port polls and connection requests to Sentral Server. (This option is only displayed in I94xx I/Port configuration screens.) Select this option to ensure that poll events, connection events, and disconnect events are not sent to Sentral Server. See Preserving I94xx Connection Mode During Discovery on page 160 for information about preserving direct mode during I/Port discovery. 154 ClearCube Technology, Inc.

167 Chapter 5: Managing Sentral Nodes Disabling Mass Storage Devices on XPe Thin Clients To disable the use of USB devices (including mass storage drives) on XPe thin clients, ensure that both of the following options are selected in the Configure Thin Client Management screen. 1. From the main menu, click Management > Thin Clients to display the Thin Clients Management screen. 2. Right-click anywhere in the screen and select Configure to display the Configure Thin Client Management screen. 3. Select the Redirect Devices option and the Forward Drives option. Select Both Options to Disable Mass Storage Devices NOTE When configuring I94xx thin clients, the Thin Client Configuration screen provides an Allow Mass Storage option. This option is not available in configuration screens for other XPe thin clients. Configuring V10LThin Clients Perform the following steps to configure a thin client or multiple thin clients. Sentral Administrator s Guide 155

168 1. Ensure that: You have run the Wyse FTP configuration utility on the Sentral FTP server, as described in Running V10L Utility on Sentral FTP Server on page 52. Your have discovered the V10L thin clients in your environment (you can discover all thin clients and select a V10L to configure, or you can restrict discovery to V10Ls on a particular subnet). 2. Right-click a thin client icon ( ) for a V10L in the Hierarchical view and select Configure Global V10L to open the Configure Global V10L Screen (you cannot create unique configurations for specific V10L thin clients; all V10L thin clients share a global configuration file). 3. Enter values or select options for the thin client or thin clients as detailed in Table 13 on page Click Save ( ) to save your changes 5. Restart each V10L that you configured by right-clicking the V10L icon in the Hierarchical view and selecting Restart. Table 14. Configure Global V10L Screen parameters. Parameter Timeout Value (min) Group REQUIRED Mapped To User Name Domain Name Color Poll Status Override Host Name Auto Connect Description This field specifies the timeout value in minutes for the thin client. The default is 10 minutes. This field specifies the name of the thin client Group, and a name must be entered. The default is CCT\. This field accepts a maximum of 50 characters. This field specifies the host or VM to whom the host is currently mapped. Name of user to log in. You can specify a user name for a single thin client only, not for multiple thin clients. Name of single or multiple Domains to log in to. Multiple Domains must be comma separated. You can specify a Domain list for a single thin client only, not for multiple thin clients. This is the color quality right inputs 8 bit, 16 bit, 24 bit Whether or not to poll in case of Connect/Disconnect from thin client agent (True/False). If set to false connect/disconnect information will be sent with the next push poll. Allows overriding the default target host name during login. The default value is unselected. Whether to reconnect after disconnection or not. True/False. 156 ClearCube Technology, Inc.

169 Chapter 5: Managing Sentral Nodes Allow Mass Storage Primary Server REQUIRED Secondary Server REQUIRED Poll Time (min) REQUIRED Host Name Password Resolution Parameter Select this option to allow users to use USB mass storage devices on thin clients. This field specifies the Primary Sentral Server. The default value is empty. If Assign Server Values is selected, this field is filled with the name of the Primary server that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Secondary Sentral Server. The default value is empty. If Assign Server Values is selected, this field is filled with the name of the Secondary server that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Host Poll Time, in minutes. The default value is 1. If Assign Server Values is selected, this field is filled with the Host Poll Time that is specified in the Console Configuration table, shown on Table 6 on page 91. Name of Host to log in to. This is the Password Value Description This is the screen resolution. Applicable resolutions depend on OS and hardware. Possible values include 320x200, 320x240, 384x512, 400x300, 480x640, 512x384, 600x600, 640x480, 768x1024, 800x600, 1024x768, 1152x864, 1280x1024. Cache Bit Map This is the setting for Bitmap Caching right inputs True, False Stop Thin Client Config Allows halting reconfiguration of this thin client during an autodiscovery. The default value is unselected. Assign Server Values Unmapped Printer Unmapped Serial This checkbox allows assigning the values stored on the Sentral Console for the Primary Server, Secondary Server, and Poll Time fields. The default value is unchecked. Whether to forward the printers information during the thin client agent session. True/False Whether to forward ports during thin client agent session or not. True/False View a Thin Client s Health and Status To view a thin client s health and status, perform the following steps: 1. From the main menu, click Management > Thin Clients to display the Thin Clients Management screen. 2. Right click anywhere in the upper portion of the screen and select View Health & Status to display the Health and Status Thin Clients screen. Sentral Administrator s Guide 157

170 3. See View Health & Status of a Selected Thin Client on page 179 for more information. NOTE Thin clients that do not use a ClearCube thin client image might display a reduced set of health and status information. Map a Thin Client to a Host To map a thin client to a host: 1. From the main menu, click Management > Thin Clients to display the Thin Clients Management screen. 2. Select and right-click a thin client that is online. From the right-click menu, select Map Thin Client to Host to display the Connection Brokering Mappings screen. See Dedicated Mappings (Thin Clients to Hosts) on page 207 for a complete procedure. Map a Thin Client to a Virtual Machine To map a thin client to a VM, perform the following steps: 1. From the main menu, click Management > Thin Clients to display the Thin Clients Management screen. 2. Select and right-click a thin client that is online. From the right-click menu, select Map Thin Client to Virtual Machine to display the Connection Brokering Mappings screen. See Dedicated Mappings (Thin Clients to Virtual Machines) on page 208 for a complete procedure. Update Thin Client Agent for a Thin Client or a Thin Client Group To update the thin client agent software on a thin client or on a group of thin clients, perform the following steps: 1. Ensure that you have: Thin Client Agent update files (an update file and an answer file) Access to the directory where the files are located 2. From the main menu, click Management > Thin Clients to display the Thin Clients Management screen. 3. Right-click anywhere in the screen and: To update one or more thin clients: Select Update Thin Client Agent 158 ClearCube Technology, Inc.

171 Chapter 5: Managing Sentral Nodes To update one or more thin client groups: Select Update Thin Client Agent Group to display the Update Thin Client Agent Management screen. Sentral displays the discovered thin clients. 4. Select and right-click one or more thin clients or thin client groups. Select New Update from the right-click menu to move the selected thin clients to the Selected Thin Client portion of the screen. 5. Click the Update File Browse button to navigate to the appropriate update file. Select the file and click Open. Sentral ignores any characters you type in this text box. 6. Click the Answer File Browse button to navigate to the appropriate answer file. Select the file and click Open. Sentral ignores any characters you type in this text box. 7. From the toolbar, click Schedule Time ( ) to display the Date Time Management screen. 8. Click the spin boxes to specify the date and time for the update to occur, and then select an interval to specify how often the update should occur. 9. From the toolbar, click the Save button. From the toolbar, click Update ( ) to set the update to run at the scheduled time. The Update and Answer files are copied to the Sentral update cache. At the designated time, Sentral performs the update. View Thin Client Equipment History To view the equipment history of a thin client, perform the following steps: 1. From the main menu, select Management > Thin Clients to display the Thin Clients Management screen. 2. Select and right-click a thin client. Select View Equipment History from the right-click menu to display the Thin Clients Management Equipment History screen. 3. Right-click a thin client and select an option from the right-click menu to add, modify, or delete equipment history reports. NOTE The Equipment History field is limited to 3,000 characters. Sentral Administrator s Guide 159

172 Preserving I94xx Connection Mode During Discovery As described in Table 13 on page 152, you must specify a connection mode when configuring I94xx I/Ports. When Sentral discovers I94xx I/Ports, Sentral always changes the I/Port s connection mode to Sentral mode. If you have one or a set of I94xx I/Ports set to direct mode and want to preserve the direct setting so it is not changed during I/Port discovery, perform the following steps: 1. Open the ServerConfiguration.xml file, located in the following directory: C:\Program Files\Apache Group\Tomcat 4.1\webapps\CMSServer\ WEBINF\configuration\properties 2. Change the set.i9400.config.value attribute to false, as shown in the following line. <entry key= set.i9400.config.value >false</entry> 3. Save the file and then restart Tomcat service. a. Click Start > All Programs > Apache Tomcat > Stop Tomcat to stop the service. b. Click Start > All Programs > Apache Tomcat > Start Tomcat to restart the service. Managing Virtual Machines The Virtual Machines screens enable you to perform the following tasks: Configure a virtual machine (VM) Edit VMs View VM health & status Map VMs to thin clients Map VMs to users Update a VM client Update a VM client group Restart a VM Shut down a VM Power on a VM Pause a VM 160 ClearCube Technology, Inc.

173 Chapter 5: Managing Sentral Nodes Unregister a VM View VM equipment history Run VM discovery Run VM Discovery To discover VMs on your subnets, perform the following steps: 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. 2. Right-click anywhere in the screen and select Run Discovery to display the Discovery screen. Sentral displays existing subnets. 3. Perform one of the following steps to specify subnets to discover: To discover VMs on all subnets: Right-click anywhere in the screen and select Discover All Subnets To discover VMs on one or multiple subnets: Select and right-click one or multiple subnets and select Discover Selected Subnets from the right-click menu. Sentral displays the Discovery Discovered Devices screen, showing all discovered VMs. NOTE With this procedure, Sentral returns only VMs discovered. To discover all nodes, use the Setup > Configuration> Run Discovery menu option from the main menu. For more information, see Discovering Sentral Nodes on page 109. You can view the inventory report to examine discovered VMs. The inventory report details each discovered device in your environment. The report contains a Type column that identifies with a VirtualMachine label. For more information about the inventory report, see Reports Inventory on page 192. Adding Hypervisor Information to the Sentral Database Before you can work with a hypervisor (such as an ESX or Xen) or any VMs, you must add information about the following to the Sentral database: The hypervisor The computer running the hypervisor Authentication credentials Sentral Administrator s Guide 161

174 Ensure that the hypervisor is set up and configured as appropriate for your environment, and then perform the following steps to add information to the Sentral database. 1. From the main menu, select the type of hypervisor: For ESX: Click Management > Virtual Machines > ESX Hosts. For Xen: Click Management > Virtual Machines > Xen Hosts 2. Right-click anywhere in the screen and select the appropriate information screen: For ESX: Select Add ESX Host Information to display the ESX Host Information screen. For Xen: Select Add Xen Host Information to display the Xen Host Information screen. 3. From the Host Information screen, right-click and select either Add ESX Host Information or Add Xen Host Information again. The text boxes in the lower portion of the screen become active. You can now add information about your hypervisor and the computer running the hypervisor. 4. In the lower portion of the screen, type the following information: Host IP The IP address of the computer running the hypervisor. Host Port The port the hypervisor uses for communication with Sentral server. For ESX: The default port is 80. For Xen: The default port is User Name The user name of the hypervisor administrator, provided during authentication to enable Sentral to communicate with the hypervisor. Password Password for the hypervisor administrator provided during authentication. This password is unencrypted. Maximum VM Represents the maximum number of VMs that you can register in Sentral. NOTE ESX Server VI client might allow you to register more VMs than specified in this field. This value specifies the maximum number of VMs you can register and manage using Sentral. 5. From the toolbar, click Save ( ). Sentral adds the information about the hypervisor to the database and details appear in the columns in the upper portion of the screen. 6. Select and right-click the host and select Check Connection to verify connectivity between Sentral Console and the hypervisor. 162 ClearCube Technology, Inc.

175 Chapter 5: Managing Sentral Nodes 7. Select and right-click the host and select Retrieve Information. Sentral obtains information about the hypervisor and the VMs. If you encounter issues, ensure that you have configured the hypervisor to communicate with Sentral. For information about how to configure ESX Server for HTTP connections, see Integrating ESX Hypervisor on page 59. For information about integrating Xen into Sentral, see Integrating Xen Hypervisor on page 61. Registering ESX VMs in the Sentral Database If you create a new ESX VM on an existing ESX instance, you must add information about the VM to the Sentral database. NOTE Before you can register an ESX VM, you must provide information to Sentral server about the ESX host on which the VM runs. For more information, see Adding Hypervisor Information to the Sentral Database on page 161. Perform the following steps from the Hierarchical view to register ESX VMs in the Sentral database. 1. Right-click the ESX server ( ) containing the VM or VMs you are registering and select Register the VMs to display all unregistered VMs on the host. 2. Sentral displays the Register a VM screen. Select and right-click one or more VMs and select Register VM on a Host. 3. Sentral displays a progress indicator and then displays a message indicating that the VM registered successfully. If you do not receive a success message, ensure that the ESX information is correct and ensure that the database connection is active as described in Adding Hypervisor Information to the Sentral Database on page 161. After receiving the success confirmation, click OK to continue. When a VM is registered successfully, it is offline and is displayed as a nonrunning VM. See Powering on a VM on this page for instructions about starting VMs. Powering on a VM Before you can power on a VM, you must: Ensure that the VM you are starting is registered with Sentral as described in Registering ESX VMs in the Sentral Database on page 163. Ensure that the hypervisor that hosts the VM is added to the database and registered with Sentral as described in Adding Hypervisor Information to the Sentral Database on page 161. Sentral Administrator s Guide 163

176 Perform the following steps to start, or power on, a VM. 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. Select and right-click a VM, and then select Power on VM in the right-click menu. OR In the Hierarchical tab, right-click an offline VM and click Power On. A VM icon containing an X in a red circle indicates an offline VM. See Hierarchical View Icons on page 68 for more information about Sentral icons in the Hierarchical view. Sentral displays a progress bar until the VM is powered on. Enabling VMs to Automatically Start and Resume In Sentral you can create groups of VMs for groups of users. To ensure that VMs in a group are immediately available for users when they log in, you can enable VMs to start automatically. Edit the SeverConfiguration.xml file located on the computer that runs Tomcat. The ServerConfiguration.xml file is located in the following directory: C:\Program Files\Apache Group\Tomcat 4.1\webapps\CMSServer\WEB- INF\configuration\properties The following table: Details parameters in the ServerConfiguration.xml file that you must modify Specifies the values you must set to enable automatic start and resume. Table 15. ServerConfiguration.xml Parameters for Automatic VM Activation Parameter <entry key="auto.vm.balancing">true</entry> <entry key="startup.active.vm">n</entry> <entry key="auto.vm.refresh.rate">n</entry> <entry key="vm.shutdown.type">2</entry> Description and Possible Values True Enables automatic power-on and automatic resume (auto-balancing). False Disables auto-balancing. Specifies the number of VMs to start when server starts. Specify any integer appropriate for your environment. Specifies the frequency, in minutes, that the autobalancing service is run. Specify any integer appropriate for your environment. 1 Shuts down VMs. 2 Pauses VMs. 164 ClearCube Technology, Inc.

177 Chapter 5: Managing Sentral Nodes Table 15. ServerConfiguration.xml Parameters for Automatic VM Activation Parameter Description and Possible Values <entry key="connecteduser.increment.threshold">n</entry> <entry key="vm.increment">n</entry> vm.increment Specifies number of VMs to start if connected users >= connecteduser.increment.threshold parameter. connecteduser.increment.threshold Number of user that must connect before n VMs are started, where n is vm.increment value. Suppose that connecteduser.increment.threshold is 10 and vm.increment is 5. In this case, if 10 users have connected since the last service run, 5 VMs are started. <entry key="connecteduser.decrement.threshold">n</entry> vm.decrement Specifies number of VMs to shut down if <entry key="vm.decrement">n</entry> connected users >= connecteduser.decrement.threshold parameter. connecteduser.increment.threshold Number of user that must disconnect before n VMs are shut down, where n is vm.decrement value. Suppose that connecteduser.decrement.threshold is 10 and vm.decrement is 5. In this case, if 10 users have disconnected since the last service run, 5 VMs are shut down. Finding All Non-Running VMs on a Host Perform the following steps to find all non-running (powered-off) VMs on a host. 1. Ensure that the hypervisor is added to the database and registered with Sentral as described in Adding Hypervisor Information to the Sentral Database on page From the main menu, display the appropriate hosts screen: For ESX: Click Management > Virtual Machines > ESX Hosts to display the Management - ESX Hosts screen. For Xen: Click Management > Virtual Machines > Xen Hosts to display the Management - Xen Hosts screen. 3. Right-click anywhere in the screen and select Non Running VMs in the rightclick menu to display the Non Running VMs screen in the lower portion of the screen. You can now right-click any VM to edit, unregister, or power on the VM. Configure a Virtual Machine To configure a VM, perform the following steps: Sentral Administrator s Guide 165

178 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. 2. Right-click anywhere in the screen and select Configure to display the Configure Virtual Machines Management screen. 3. Select a VM. Sentral populates the text boxes in the lower portion of the screen with the values of the selected virtual machine. 4. Enter values for the parameters described in the following table. Table 16. VM Configuration Fields Field Name Timeout Value (min) Group REQUIRED FIELD Mapped To Asset Tag Stop VM Access Block Auto Config Primary Server REQUIRED FIELD Secondary Server REQUIRED FIELD Poll Time (min) REQUIRED FIELD Alert Eval Time (min) REQUIRED FIELD Alert Firing Time (hr) REQUIRED FIELD Description This field specifies the timeout value in minutes for the VM. The default is 10 minutes. This field specifies the name of the Chassis Group, and a name must be entered. The default is CCT\. This field accepts a maximum of 50 characters. This field specifies the user or thin client to whom the VM is currently mapped. This is a user-definable field. The default value is empty. This checkbox allows halting access to this VM. The default value is unchecked. This checkbox allows blocking auto-configuration actions by the Sentral Console. The default value is unchecked. This field specifies the Primary Sentral Server. The default value is empty. If the Assign Server Values checkbox is checked, this field is filled with the name of the Primary server that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Secondary Sentral Server. The default value is empty. If the Assign Server Values checkbox is checked, this filed is filled with the name of the Secondary server that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the VM Poll Time in minutes. The default value is 1. If the Assign Server Values checkbox is checked, this field is filled with the Poll Time that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the Alert Evaluation Interval in minutes. The default value is 30. If the Assign Server Values checkbox is checked, this field is filled with the Alert Evaluation Interval that is specified in the Console Configuration table, shown on Table 6 on page 91. This field specifies the time interval after which an Alert is fired. The default value is 1 hour. 166 ClearCube Technology, Inc.

179 Chapter 5: Managing Sentral Nodes Table 16. VM Configuration Fields (continued) Field Name Description Assign Server Values When checked, this checkbox maps the default values from the Sentral Console into the following fields: Primary Server, Secondary Server, Poll Time (min), Alert Eval. Time (min), and Alert Firing Time (hr). The default value is unchecked. 5. From the toolbar, click Save to save the changes, or click Cancel to discard them. Understanding VM Health and Status Information This section describes the VM health and status information that Sentral displays. For instructions about how to display the information, see View Health & Status of a Selected VM on page 183. The upper portion of the Health and Status Virtual Machines screen displays the following information. Hostname The name of the Host on which the VM is running. IP Address The IP address of the Host on which the VM is running. Status Indicates if the VM is online or offline. Possible values are: online VM is sending heartbeat to server offline VM is not sending heartbeat to server Model Code Name Indicates the type of host on which the VM is running. Possible values are: ESX ESX Server VMWare VMware Server (formerly GSX) Xen Xen hypervisor Group Indicates the name of the Chassis Group to which the VM belongs. The default is CCT\. Serial Number A unique identifier for VMs. Health Status Possible values are: OK Sentral has received a heartbeat from the VM within the interval specified in the Host Update Timeout(min) field, located on the Setup - Configuration screen. WARNING Sentral has not received a heartbeat from the VM within the interval specified in the Host Update Timeout(min) field, located on the Setup - Configuration screen. Sentral Administrator s Guide 167

180 ALERT An alert is deployed on this VM. Alerts Indicates the number of alerts deployed on this VM. For more information about VM alerts, see View Alerts for a VM on page 184. Host Displays the name of the host on which the selected VM runs. Connected Indicates if a user is logged into a VM. Possible values are: On User is logged in to the VM Off User is not logged in to the VM You can view information about registered VMs only. For information about registering VMs, see Registering ESX VMs in the Sentral Database on page 163. Map a Virtual Machine to a Thin Client To map a VM to a thin client, perform the following steps: 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. 2. Right-click anywhere in the screen and select Map Virtual Machine to Thin Client to display the Connection Brokering Mappings screen. 3. From the appropriate tabs in the screen, select a thin client and a VM and click Allocate. See Dedicated Mappings (Thin Clients to Virtual Machines) on page 208 for detailed instructions. Map a Virtual Machine to a User To map a VM to a user, perform the following steps: 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. 2. Right-click anywhere in the screen and select Map Virtual Machine to Thin Client to display the Connection Brokering Mappings screen. 3. From the appropriate tabs in the screen, select a user and a VM and click Allocate. See Dedicated Mappings (Users to Virtual Machines) on page 210 for detailed instructions. Update Client Software (Host Agent) for a Virtual Machine or a Virtual Machine Group To update the client software, or Host Agent, for a VM, perform the following steps: 168 ClearCube Technology, Inc.

181 Chapter 5: Managing Sentral Nodes 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. 2. Right-click anywhere in the screen and select one of the following: For one or multiple VMs: Select Update VM Client to display the Update VM Client Management screen. OR For a VM group: Select Update VM Client Group to display the Update VM Client Group Management screen. These screens shows all discovered VMs. 3. Select one or more VMs or VM groups and right-click an empty area in the screen. From the right-click menu, select New Update. Sentral moves the selected VMs to the Selected Virtual Machine area in the lower portion of the screen. 4. Click the Update File Browse button to navigate to the appropriate update file. Select the file and click Open. 5. Click the Answer File Browse button to navigate to the appropriate answer file. Select the file and click Open. 6. From the toolbar, click Schedule Time ( ) to display the Date Time Management screen. 7. Click the spin boxes to specify the date and time for the update to occur, and then select an interval to specify how often the update should occur. 8. From the toolbar, click the Save button. From the toolbar, click Update ( ) to set the update to run at the scheduled time. The Update and Answer files are copied to the Sentral update cache. At the designated time, Sentral performs the update. Shut Down or Restart a VM To shut down or restart a VM, perform the following steps: 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. 2. Select and right-click a VM. From the right-click menu, select Restart VM to restart a VM, or click Shutdown VM to shut down a VM. View Equipment History for a VM To view the equipment history for a VM, perform the following steps: Sentral Administrator s Guide 169

182 1. From the main menu, click Management > Virtual Machines > All Virtual Machines to display the Virtual Machines Management screen. 2. Select and right-click a VM. From the right-click menu, select View Equipment History to display the VMs Equipment History Management screen. 3. Use the right-click menus to add, modify, or delete equipment history reports. NOTE The Equipment History field is limited to 3,000 characters. 170 ClearCube Technology, Inc.

183 Chapter 5: Managing Sentral Nodes Managing Users The Users screens enable you to: Configure a user Create a mapping for a user Discover users in your Sentral environment Discover Users in the Sentral Environment To run user discovery, perform the following steps: 1. From the main menu, select Management > Users to display the Users Management screen. 2. Right-click anywhere in the screen and select Run Discovery to display the Discovery screen. This screen displays existing subnets. 3. Right-click anywhere in the screen and select Discover Users to display the Available Security Group(s) dialog box. 4. Select one or multiple security groups to discover and click Submit. The Discovered Users screen displays the discovered users. NOTE With this procedure, Sentral returns only users discovered. To discover all nodes, use the Setup > Configuration > Run Discovery menu option from the main menu. For more information, see Discovering Sentral Nodes on page 109. Adding an Asset Tag to a User You can add an asset tag to a user in a Sentral user group. This asset tag can be any descriptive, meaningful text. To add an asset tag, perform the following steps: NOTE Before you can add an asset tag to a user, the user must be a member of a Sentral user group. See Adding Local and Domain Security Groups to Sentral User Groups on page 174 for more information. 1. From the main menu, select Management > Users to display the Users Management screen. 2. Select and right-click a user. Select Configure to display the Configure Users Management screen. Sentral Administrator s Guide 171

184 3. The bottom portion of the screen displays details about the user. The following table details each text box. Table 17. User Configuration Fields Field Name Group Location Mapped To Asset Tag Description This static field specifies the name of the group to which the user belongs. This static field specifies the group hierarchy for the user s group. This static field specifies the host or VM to which the user is mapped (if any). This editable field allows adding information about the user. The default value is empty. 4. Type any descriptive text in Asset Tag text box. 5. From the toolbar, click Save ( ), and then click OK to close the confirmation dialog box. Additionally, you can create mappings for the selected user by clicking the toolbar buttons. See Dedicated Mappings (Users to Virtual Machines) on page 210 for more information. Configuring Sentral for User Based Mapping The following sections describe configuration settings to set for the different types of user-based mappings in Sentral. Windows Based User Mapping Sentral supports Active Directory (AD) user based mapping. If an AD security group is mapped to a resource group in Sentral, users in AD security groups can log in and receive host allocations based on mappings you create in Sentral. To enable Windows based user mappings in Sentral, ensure that: Mapping User Type is set to Windows. From the main menu, click Setup > Configuration to open the Configuration screen. The Mapping User Type dropdown menu is located on this screen. After making the change, click Save ( ) in the toolbar. Connection Preference is set to User. From the main menu, click Setup > Configuration to open the Configuration screen. The Connection Preference drop-down menu is located on this screen. After making the change, click Save ( ) in the toolbar. You have created mappings between a user and a host group. See Dedicated Mappings (Users to Hosts) on page 209 for more information. 172 ClearCube Technology, Inc.

185 Chapter 5: Managing Sentral Nodes Sentral Based Mapping You can import users into Sentral from Active Directories or by using a Sentral-based mapping. To use Sentral-based mappings, ensure that: Mapping User Type is set to Sentral. From the main menu, click Setup > Configuration to open the Configuration screen. The Mapping User Type dropdown menu is located on this screen. After making the change, click Save ( ) in the toolbar. Connection Preference is set to User. From the main menu, click Setup > Configuration to open the Configuration screen. The Connection Preference drop-down menu is located on this screen. After making the change, click Save ( ) in the toolbar. You have created mappings between a user and host groups. See Dedicated Mappings (Users to Hosts) on page 209 for more information. You can also map thin clients to physical hosts and to VMs. This allows for the mapping to be device-specific rather than user-specific. Configuring Sentral for Device Based Mapping To map thin clients to a host or to a host group, ensure that: Mapping User Type is set to Sentral or Windows, as appropriate for your environment. From the main menu, click Setup > Configuration to open the Configuration screen. The Mapping User Type drop-down menu is located on this screen. After making the change, click Save ( ) in the toolbar. Connection Preference is set to Thin Clients. From the main menu, click Setup > Configuration to open the Configuration screen. The Connection Preference drop-down menu is located on this screen. After making the change, click Save ( ) in the toolbar. You have created mappings between a thin client and a host group. See Dedicated Mappings (Thin Clients to Hosts) on page 207 and Dedicated Mappings (Thin Clients to Virtual Machines) on page 208 for more information. Create a Mapping for a User To crate a mapping for a user, perform the following steps: 1. From the main menu, select Management > Users to display the Users Management screen. 2. Select and right-click a user. Select Create Mapping from the right-click menu to display the Connection Brokering Mappings screen. See Dedicated Mappings (Users to Hosts) on page 209 or Dedicated Mappings (Users to Virtual Machines) on page 210 for more information. Sentral Administrator s Guide 173

186 Adding Local and Domain Security Groups to Sentral User Groups To add a Windows security group to a Sentral user group, you must: Ensure your user discovery and mapping specifications are appropriate. Add the Windows security group to a Sentral user group. Perform the following steps: 1. From the main menu, click Setup > Configuration. 2. From the Discovery User Preference drop-down menu, select Local or Domain, as appropriate. See Specifying the User Type to Discover on page 114 for more information. 3. Select one of the following, as appropriate, from the Mapping User Type dropdown menu (see Configuring Sentral for User Based Mapping on page 172 for more information). Sentral A group you create in Sentral. Windows An Active Directory group. 4. From the main menu click Management > Groups to display the Connection Brokering - Groups screen. Right-click anywhere in the screen and select Add Local/Domain Groups to display the Connection Brokering - Groups (Add) screen. 5. From the upper portion of the screen: a. Select one or multiple security groups to add to a Sentral user group. b. Right-click your selection and select Add Selected Groups. Sentral displays the groups in the Add group(s) portion of the screen. 6. From the Group Type drop-down menu, select one of the following: Shared Connects the user to any available host or VM in a shared host group. Spared Allows switching users to any available spare host (including VMs) in the event of a host or VM failure. 7. Select the target Sentral group in the Select Target Group area. 8. From the toolbar, click Add ( ), and then click OK to close the confirmation screen. The security group is now displayed in the Hierarchical view. 174 ClearCube Technology, Inc.

187 Chapter 5: Managing Sentral Nodes Managing Views You can create views in Sentral to display any collection of nodes that you specify. For example, you could create a view to display all nodes in a geographical region of your enterprise, or you could create a view to display only the thin clients on a particular floor of a building. The Views Management screen enables you to: Add a view Modify a view Delete a view Figure 53. Management Views Screen Add a View To add a new view, perform the following steps: 1. From the main menu, click Management > Views to display the Views Management screen. 2. Right-click anywhere in the screen and select Add new View. Sentral displays all discovered nodes in the lower left portion of the screen. 3. Type a name for the view in the View Name text box. 4. From the left column, select one or multiple nodes to include in the view. Sentral Administrator s Guide 175

188 5. Click the Add button ( ) to move each node to the right column. The right column contains all nodes that will be shown in the view you are creating. To remove a node from the view, select the node and click Remove ( ). 6. Click Save ( ) to create the view. You can now select the view at any time from the View drop-down menu in the upper right portion of the screen. Modify a View To modify a view, perform the following steps: 1. From the main menu, select Management > Views to display the Views Management screen. 2. Select and right-click a view in the Defined Views column in the upper portion of the screen. Select Modify View from the right-click menu. Sentral displays the view in the lower portion of the screen, and shows the nodes currently contained in the view in the lower right area. 3. Add and remove nodes from the view as described in Add a View on this page. 4. From the toolbar, click Save ( ). Delete a View To delete a view, perform the following steps: 1. From the main menu, select Management > Views to display the Views Management page. 2. Select and right-click a view in the Defined Views column in the upper portion of the screen. Select Delete View from the right-click menu. 3. Click Yes to delete the view, and then click OK to close the confirmation dialog box. Health & Status Tasks The Health & Status menu enables you to view and manage the following: Hosts Thin clients Virtual Machines Chassis 176 ClearCube Technology, Inc.

189 Chapter 5: Managing Sentral Nodes Alerts The following table shows which of these menu items are displayed, depending on the Sentral modules activated on your system. Table 18. Management Menu Items Displayed by Module Management Menu Items C = Console D = Connection Brokering Module S = Switching Module V = Virtual Machine C C + D C + S C + D + S C + D + S + V Chassis X X X Hosts X X X X X C/Ports X X X Thin clients X X X Virtual Machines X Users X X X Views X X X X X Health & Status Chassis The Chassis submenu enables you to: View health and status of a selected chassis Update a chassis firmware View equipment history for a chassis View Alerts for a chassis View Health and Status of a Selected Chassis To view the health and status of a chassis, perform the following steps: 1. From the main menu, click Health & Status > Chassis to display the Health and Status Chassis screen. 2. Select and right-click a chassis in the upper portion of the screen. Sentral Administrator s Guide 177

190 3. Select View health and status of selected chassis from the right-click menu, and Sentral displays chassis information in the Inventory Details tab, located in the lower portion of the screen. Figure 54. Health and Status Chassis Screen Update a Chassis Firmware To update a chassis firmware, perform the following steps: 1. From the main menu, click Health & Status > Chassis to display the Health and Status Chassis screen. 2. Select and right-click a chassis in the upper portion of the screen. 3. Select Update Firmware to display the Chassis Update Firmware Management screen. 4. Perform the steps described in Update Chassis Firmware on page 128. View Equipment History for a Chassis To view the equipment history for a chassis, perform the following steps: 1. From the main menu, click Health & Status > Chassis to display the Health and Status Chassis screen. 2. Select and right-click a chassis in the upper portion of the screen. 178 ClearCube Technology, Inc.

191 Chapter 5: Managing Sentral Nodes 3. Select View Equipment History to display the Health & Status - Chassis Equipment History screen. If equipment history exists, it is displayed. From rightclick menus and the toolbar, you can add, modify, and delete equipment history. NOTE The Equipment History field is limited to 3,000 characters. View Alerts for a Chassis To view alerts for a chassis, perform the following steps: 1. From the main menu, click Health & Status > Chassis to display the Health and Status Chassis screen. 2. Select and right-click a chassis in the upper portion of the screen. 3. Select View Alerts to display the Reports Alerts screen. See Reports Tasks on page 191 for information about generating and viewing reports. NOTE The Alerts/Logs tab in the lower portion of the screen displays information about RMM alerts and logs, while the Reports - Alerts screen displays alerts that you configure in Sentral. Health & Status Thin Clients The Health & Status > Thin Clients submenu enables you to: View health and status of a selected thin client View equipment history for a thin client NOTE This menu item is available only if the Connection Brokering module is activated. NOTE Thin clients that do not use a ClearCube thin client image might display a limited set of health and status information. View Health & Status of a Selected Thin Client To obtain health and status information about a thin client, perform the following steps. 1. Ensure that you have discovered the thin clients in your enterprise. To restrict the set of thin clients you discover, you can perform a discovery on one or on a set of subnets, as described in Discovering Sentral Nodes on page From the main menu, click Health & Status > Thin Clients to display the Health and Status - Thin Clients screen. Sentral Administrator s Guide 179

192 3. Select and right-click a thin client in the upper portion of the screen, and then select View health and status of selected Thin Client. Details about the thin client appear in lower portion of the screen under Selected Thin Client. NOTE You can only receive information about thin clients that display online in the Status column. NOTE V10L thin clients do not report health and status information. Available information categories include: Table 19. Possible Thin Client Health and Status Categories XPe Thin client NeoLinux Thin client System Information Memory Motherboard Processor BIOS Network Memory Drives Network Processor System Information Operating System Asset Management Drives Operating System 180 ClearCube Technology, Inc.

193 Chapter 5: Managing Sentral Nodes Figure 55. Health and Status Thin Clients Screen View Equipment History for a Thin Client To view the equipment history for a thin client, perform the following steps: 1. From the main menu, select Health & Status > Thin Clients to display the Health and Status Thin Clients screen. 2. From the upper portion of the screen, select and right-click a thin client. 3. Select View Equipment History. Equipment history, if available, is displayed in the Health & Status - Thin Clients Equipment History screen. Sentral Administrator s Guide 181

194 4. From right-click menus or from the toolbar, you can add, modify, or delete equipment history. NOTE The Equipment History field is limited to 3,000 characters. Health & Status Hosts The Health & Status > Hosts submenu enables you to: View health and status of a selected host View equipment history for a host View Alerts for a host View Health and Status of a Selected Host To view the health and status for a host, perform the following steps: 1. From the main menu, select Health & Status > Hosts to display the Health and Status Hosts screen. 2. In the upper portion of the screen, select and right-click a host. 3. Select View health and status of selected host. Sentral displays host information in the Selected Host portion of the screen. 4. Click any of the tabs to display host specific information. View Equipment History for a Host To view the equipment history for a host, perform the following steps: 1. From the main menu, select Health & Status > Hosts to display the Health and Status Hosts screen. 2. In the upper portion of the screen, select and right-click a host. 3. Select View Equipment History. Equipment history, if available, is displayed in the Health & Status - Thin Clients Equipment History screen. 4. From right-click menus or from the toolbar, you can add, modify, or delete equipment history. NOTE The Equipment History field is limited to 3,000 characters. 182 ClearCube Technology, Inc.

195 Chapter 5: Managing Sentral Nodes View Alerts for a Host See Health & Status Alerts on page 184 for more information about alerts. To view alerts for a host, perform the following steps: 1. From the main menu, click Health & Status > Hosts to display the Health and Status Host screen. 2. Select and right-click a host in the upper portion of the screen. 3. Select View Alerts to display the Reports Alerts screen. See Reports Tasks on page 191 for information about generating and viewing reports. Health & Status Virtual Machines The Virtual Machines sub-menu allows you to perform the following tasks for Virtual Machines (VMs): View health and status of a selected VM View equipment history for a VM View alerts for a VM The functionality of this menu choice is essentially identical to the Health and Status Hosts choice, except that information regarding VMs is displayed. View Health & Status of a Selected VM To display health and status information for a virtual machine: 1. From the main menu, select Health & Status > Virtual Machines to display the Health and Status Virtual Machines screen. 2. In the upper portion of the screen, select and right-click a VM. 3. Select View health and status of selected virtual machine. Sentral displays VM information in the Selected Virtual Machine portion of the screen. Click any of the tabs to display VM specific information. For details about the information displayed in the health and status screen, see Understanding VM Health and Status Information on page 167. View Equipment History for a VM To view the equipment history for a VM, perform the following steps: Sentral Administrator s Guide 183

196 1. From the main menu, select Health & Status > Virtual Machines to display the Health and Status Virtual Machines screen. 2. In the upper portion of the screen, select and right-click a VM. 3. Select View Equipment History. Equipment history, if available, is displayed in the Health & Status - Virtual Machines Equipment History screen. 4. From right-click menus or from the toolbar, you can add, modify, or delete equipment history. NOTE The Equipment History field is limited to 3,000 characters. View Alerts for a VM See Health & Status Alerts on page 184 for more information about alerts. To view Alerts for a VM, perform the following steps: 1. From the main menu, click Health & Status > Virtual Machines to display the Health and Status Virtual Machines screen. 2. Select and right-click a VM in the upper portion of the screen. 3. Select View Alerts to display the Reports Alerts screen. See Reports Tasks on page 191 for information about generating and viewing reports. Health & Status Alerts Alerts allow a computing resource to report an abnormal condition such as low disk space or an overheating system. Alerts are deployed by computing resources only, because the health and status reporting capabilities are embedded in the Sentral Host Agent. Using alerts that you create, you can configure Sentral to perform specific actions on hosts in certain conditions. For example, you can monitor any combination of the following aspects: Free memory Disk space Installed applications Free virtual memory Voltage Fan speed ClearCube blade temperature 184 ClearCube Technology, Inc.

197 Chapter 5: Managing Sentral Nodes ClearCube blade fan speed ClearCube blade voltage When these aspects meet the conditions or thresholds that you specify, you can configure Sentral to perform any logical combination of the following: a specified address Shut down the host Restart the host If you create an alert that monitors more than one host condition, all of the conditions must be met before Sentral performs the specified action. For example, suppose you create an alert that: Fires an alert when host temperature is greater than or equal to 50 degrees Celsius Fires an alert when host fan speed is less than or equal to 1000 RPM Shuts down a host when the specified thresholds are met. Sentral does not shut down the host until both conditions are met. After you create an alert, you must deploy the alert to each host or host group that contains host you want to monitor. Sentral does not monitor the host until you explicitly deploying the alert to the host or host group. The Health & Status > Alerts submenu enables you to: View alerts Configure alerts View deployed alerts View Alerts To view alerts, perform the following steps: 1. Form the main menu, click Health & Status > Alerts > View Alerts to display the Reports - Alerts screen. 2. You can view alert information in this screen. Optionally, select and right-click an alert to display the right-click menu. The right-click menu provides the following options: View All Logging View Deployed Alerts Sentral Administrator s Guide 185

198 Configure Alerts Inventory Report Clear All Alerts Clear Selected Alert Scheduler Report Export Report Export Selected Reports Connection History Configure Alerts The Configure Alerts screen enables you to: Create customized alerts Deploy alerts to: VMs and VM groups Hosts and host groups Modify and delete alerts 186 ClearCube Technology, Inc.

199 Chapter 5: Managing Sentral Nodes The following figure shows the Configure Alerts screen. Figure 56. Health & Status Configure alerts screen with threshold specification dialog box Add a New Alert To add an alert, perform the following steps: 1. From the main menu, click Health & Status > Alerts > Configure Alerts to display the Health and Status Configure Alerts screen. 2. Select an item to monitor in the Monitor panel. Sentral either displays an input dialog box where you can enter an appropriate value, or Sentral activates the Evaluate panel. If you need to change the Monitor item, click Cancel ( ) from the toolbar to return to the Monitor panel. 3. Select an item in the Evaluate panel or in the Monitor dialog box if it is displayed. Sentral displays the Evaluate Input dialog box, where you specify a threshold value for the alert. Click OK to accept the value, or click Cancel to start over. Sentral Administrator s Guide 187

200 4. Optionally, add additional items to monitor by repeating Step 2 and Step Select an item in the Action panel. a. If you select , the Action Input dialog box is displayed, allowing you to enter an address to receive the alert notification. b. You can select more than one action. Multiple actions are executed in the order specified. Since the alert is processed on and sent from the machine where the actions are executed, the Shutdown and Restart actions prevent any further actions from occurring. 6. Type a name for the alert in the Name text box. 7. Optionally, if you use SNMP in your enterprise, select the SNMP Alert option to save this as an SNMP alert. 8. From the toolbar, click Save ( ). The alert is saved and listed in the upper portion of the screen. You must explicitly deploy the alert to a host or host group to enable Sentral to monitor the device. See the following section for instructions about how to deploy an alert. Deploy an Alert To deploy an Alert, perform the following steps: 1. From the main menu, click Health & Status > Alerts > Configure Alerts to display the Health and Status Configure Alerts screen. 2. Select and right-click an alert. Select one of the following deployment choices: Deploy to Host Group Deploy to VM Group Deploy to Host Deploy to VM The appropriate Health & Status Deploy screen is displayed, depending on your selection. All the available nodes or groups are listed. 3. Select a group or node to receive the alert. With your keyboard and mouse, CTRL-Click or Shift-Click to select multiple nodes, or press CTRL-A to select all nodes. 4. Right-click your selection and select Deploy Alert. 5. Click OK to close the confirmation dialog box. 188 ClearCube Technology, Inc.

201 Chapter 5: Managing Sentral Nodes Notes: When the alert is saved, it is only entered into the Configured Alerts table. It is not activated until it is deployed to a host agent. If you want to cause multiple actions to occur, you can select several items before saving the alert. If you want to specify several Evaluate conditions, select a Monitor value and an Evaluate value for each of the conditions. For example, you cannot check for a condition of Memory >= 100 MB and <= 200 MB. In this example, you need to establish a separate entry for each condition, as Memory >= 100 MB and Memory <= 200 MB. The conditions must all test true for the alert to fire. To set an either/or condition, deploy distinct alerts, one for each condition. Then when any of the conditions is true, the corresponding alert is deployed. With one exception, all the Evaluate values are numeric, and may include decimal places. For Installed Applications, the value is a string that must (except for upper/ lower case) exactly match the name of the software application as found in Windows Control Panel, under Add/Remove Programs. The Actions panel includes Shutdown and Restart items. If an alert deploys a shutdown or restart, you can abort the action using a DOS command prompt. When you receive a notification that a shutdown is in progress, you have 30 seconds by default (configurable to other values) to open a command prompt and execute the shutdown a command to abort the shutdown. Modifying Alerts As described in Health & Status Alerts on page 184, alerts can monitor one or multiple conditions of a host. The following sections describe how to modify alerts that monitor one or multiple host conditions. NOTE Modifying an alert does not cause a host to activate it. Changes do not take effect until the alert is deployed to a host. Modifying Alerts that Monitor a Single Condition 1. From the main menu, click Health & Status > Alerts > Configure Alerts to display the Health and Status Configure Alerts screen. 2. From the upper portion of the screen, select and right-click an alert to modify (you can modify one alert at a time). Select Modify Alert. The existing alert configuration is displayed in the lower portion of the screen. 3. Select a new Monitor item, a new Evaluate item, or both. If you select a new item in the Evaluate area, specify a new value in the dialog box and then click OK. 4. Optionally, to specify a new action for the alert to perform, click Next Item ( ) in the toolbar and then select an action. Sentral Administrator s Guide 189

202 5. Sentral displays the Action Input dialog box. If you are specifying a new address, type the address and click OK. If you are selecting the Shutdown or Restart action, leave the dialog box empty and click OK. 6. From the toolbar, click Save ( ) and then click OK to close the confirmation dialog box. You can see the description of the updated alert in the Description column located in the upper part of the screen. 7. Deploy the alert as described in Deploy an Alert on page 188. Modifying Alerts that Monitor Multiple Conditions 1. From the main menu, click Health & Status > Alerts > Configure Alerts to display the Health and Status Configure Alerts screen. 2. From the upper portion of the screen, select and right-click an alert to modify (you can modify one alert at a time). Select Modify Alert. The existing alert configuration is displayed in the lower portion of the screen. 3. From the toolbar, click Previous Item ( ) and Next Item ( ) to move between each item, where an item is a grouping of the following: The host condition to monitor AND The value that triggers the alert 4. Change values of existing Monitor items, Evaluate items, or both. 5. To add and item, click Add Item ( ) and select a Monitor and Evaluate pair. Optionally, specify a discreet action in the Action panel for that item. 6. To remove an item (that is, a condition to Monitor and a value to Evaluate), click Previous Item ( ) or Next Item ( ) until the item you want to remove is highlighted. Click Remove Item ( ). 7. Optionally, change one or multiple alert actions by clicking Next Item ( ) until the item in the Action panel is highlighted. Select the new action and click Save ( ). 8. Deploy the alert as described in Deploy an Alert on page 188. If the alert has been deployed previously, deploy it again to apply the changes to the host or host group. The modified alert overwrites the previously deployed alert. 190 ClearCube Technology, Inc.

203 Chapter 5: Managing Sentral Nodes Removing Alerts from Sentral Console To remove an alert from the console, perform the following steps: NOTE Deleting an alert from Sentral console does not delete the alert from the host. To delete an alert from a host after the alert is deployed to the host, you must delete the alert using the Host Agent. See Delete Alerts on the Host Agent on page 252 for more information. 1. From the main menu, click Health & Status > Alerts > Configure Alerts to display the Health and Status Configure Alerts screen. 2. Select one or multiple alerts. Right-click your selection and select Delete Alert. 3. Click OK to close the confirmation screen. View Deployed Alerts To view deployed alerts, perform the following steps: 1. From the main menu, click Health & Status > Alerts > View Deployed Alerts to display the Health and Status View Deployed Alerts screen. 2. Select and right-click one or multiple alerts. 3. From the Tasks menu, select one of the following: Clear Selected Log Clear All Logs Export Logs Mute Selected Alerts Un-Mute Selected Alerts Delete Selected Alerts Reports Tasks Reports display information about individual devices in Sentral. The Reports menu provides the following reporting capabilities: Inventory Alerts Custom Reports Equipment History Sentral Administrator s Guide 191

204 Device Accessibility All choices are activated in the Console. Reports Inventory The Reports > Inventory submenu enables you to perform the following tasks for discovered nodes: Create inventory reports Export inventory reports Schedule the time to run an inventory report The following figure shows the Reports - Inventory screen. Figure 57. Reports - Inventory screen Sentral: Tracks the start and stop times of the connection that users make to hosts and VMs Tracks the connection state transition The following menu items explain the individual tasks in more detail. Perform the following steps to create and export an inventory report. 1. From the main menu, select Reports > Inventory to display the Reports Inventory screen. 2. Select and then right-click one or multiple device entries. Select Schedule Time to display the Date Time Management screen. 192 ClearCube Technology, Inc.

205 Chapter 5: Managing Sentral Nodes 3. Click the spin boxes to specify a date and starting time, in the future, to create a report. 4. Select an interval at which to create reports. 5. From the toolbar, click Save ( ). Sentral displays the Reports - Inventory screen again. 6. Ensure that at least one of the selected devices remains highlighted. Right-click the selection and select Schedule Report. Click OK to close the confirmation dialog box. 7. Ensure that at least one of the selected devices remains highlighted. Sentral briefly displays Windows command prompt when the report is generated. Right-click the selection and select Export Report. 8. Specify a name and location to save the XML report. Click Save and then click OK to close the confirmation dialog box. NOTE To export a report, you must be logged in to Sentral with Administrator privileges on the Sentral console system with the user ID specified in the System User Name and System User Password parameters in the Setup Configuration screen. See Setting Global Configurations for Sentral on page 87 for more information. Reports Alerts The Reports > Alerts submenu enables you to perform the following tasks for discovered nodes: Produce alerts reports Export alerts reports You can export Alerts reports in MIF, XML, and CVS formats. NOTE When exporting logs, you can export only one page of logs at a time. Scroll to the page containing the desired log(s) to export, and export that page. Schedule the time to run an alerts report 1. From the main menu, click Reports > Alerts to display the Reports Alerts screen. 2. Select one or multiple entries from the list. 3. Right-click the selection and select one of the following: View All Logging View Deployed Alerts Sentral Administrator s Guide 193

206 Configure Alerts Inventory Report Clear All Alerts Clear Selected Alert Scheduler Report Export Report Export Selected Reports Connection History View Logging To view logging, perform the following steps: 1. From the main menu, select Reports > Alerts to display the Reports Alerts screen. 2. Right-click anywhere in the screen and select View All Logging. This screen displayed contains logs that detail the actions that all Sentral users perform. 3. Select one or more logs to work with, and choose an item from the menu. Available tasks in the menu include: Clear Selected Log Clear All Logs Export Logs You can export logs in MIF, XML, and CVS formats. View Deployed Alerts To view deployed alerts, perform the following steps: 1. From the main menu, select Reports > Alerts to display the Reports Alerts screen. 2. Right-click anywhere in the screen and select View Deployed Alerts. 3. Select one or more alerts and right-click your selection. Choose any of the following menu options: Clear Selected Log Clear All Logs Export Logs 194 ClearCube Technology, Inc.

207 Chapter 5: Managing Sentral Nodes Mute Selected Alerts Un-Mute Selected Alerts Delete Selected Alerts Configure Alerts To configure alerts, perform the following steps: 1. From the main menu, click Reports > Alerts to display the Reports Alerts screen. 2. Right-click anywhere in the screen and select Configure Alerts to display the Health & Status - Configure Alerts screen. Continue by performing the steps described in Health & Status Alerts on page 184. Inventory Report To generate an inventory report, perform the following steps: 1. From the main menu, click Reports > Alerts to display the Reports Alerts screen. 2. Right-click anywhere in the screen and select Inventory Report to display the Reports - Inventory screen. This screen displays a list of discovered nodes. 3. Continue by performing the steps described in Reports Inventory on page 192. Clear All Alerts To clear all Alerts, perform the following steps: 1. From the main menu, click Reports > Alerts to display the Reports Alerts screen. 2. Right-click anywhere in the screen and select Clear All Alerts. Click Yes and then click OK to close the confirmation dialog box. Clear Selected Alerts To clear selected Alerts, perform the following steps: 1. From the main menu, click Reports > Alerts to display the Reports Alerts screen. 2. Select one or multiple entries from the list. Right-click your selection and select Clear Selected Alert. Sentral Administrator s Guide 195

208 3. Click Yes and then click OK to close the confirmation dialog box. Scheduler Report The scheduler report displays information about all reports that have been successfully scheduled. To view a scheduler report, perform the following steps: 1. From the main menu, click Reports > Alerts to display the Reports Alerts screen. 2. Right-click anywhere in the screen and select Scheduler Report to display the Reports Scheduler Log screen. 3. To clear a scheduled event, select and right-click an entry. Select Clear Selected Schedule. To clear all scheduled events, right-click and select Clear All Schedule. NOTE In this screen, a dialog box to confirm or cancel your action is not provided. Schedules are cleared when you choose a Clear task. Use the back button or make a new choice from the main menu if you do not wish to clear any events. Reports Custom Reports The Reports > Custom Reports submenu enables you to produce customized reports for discovered nodes. You can select from the following parameters: Host Name IP Address Type (of discovered node) MAC Address Serial Number (if available C/Ports do not report their serial numbers) Dedicated Node Status (dedicated or shared) CPU Load (percentage) Memory Load (percentage) Number of Connections to the Node Shared Allocation Spare Allocation 196 ClearCube Technology, Inc.

209 Chapter 5: Managing Sentral Nodes Domain Name Security Groups To generate a custom report, perform the following steps: 1. From the main menu, click Reports > Custom Reports to display the Reports Custom Reports screen. 2. Select and right-click a report. Select Export Report to display the Save dialog box. 3. From the Files of type drop-down menu, specify the format in which to save your report by selecting one of the following: *.csv saves the exported report as a CSV file *.xml saves the exported report as a XML file *.mif saves the exported report as a MIF file 4. Specify a file name in the File name dialog box. 5. Click Save and then click OK to close the confirmation dialog box. Reports Equipment History The Reports > Equipment History submenu enables you to: Export equipment history reports Delete equipment history records Export Equipment History Report To export an equipment history report, perform the following steps: 1. From the main menu, click Reports > Equipment History to display the Reports Equipment History screen. 2. Select and right-click a report. Select Export Report. You can save the exported file as a.csv,.xml, or.mif file. Delete Equipment History To delete equipment history, perform the following steps: 1. From the main menu, click Reports > Equipment History to display the Reports Equipment History screen. Sentral Administrator s Guide 197

210 2. Select and right-click an entry. Select Delete Selected History. Click Yes, and then click OK to close the confirmation dialog box. Reports Device Accessibility The following figure shows the Reports - Device Accessibility screen. Figure 58. Reports - Device Accessibility screen This report details: The discovered devices in your Sentral environment. The protocols that can connect to the device The following list details each protocol displayed in the Reports - Device Accessibility screen and they user ports that use the protocols. TDXA I8330 RDP TDXD C/Ports PCoIP I94xx Thin clients 198 ClearCube Technology, Inc.

211 Chapter 6: Using Intel Active Management Technology You can use Intel Active Management Technology (AMT) on ClearCube A1410 blades to manage the blades out-of-band. AMT enables hardware-level access to an A1410 if it is inserted in a chassis and connected to an Ethernet network. AMT-level communication occurs independent of any operating system state; that is, the A1410 must be connected to power but it does not have to be powered on to perform AMT tasks. You must enable AMT in an A1410 before you can use AMT features. This chapter describes: How to provision AMT on A1410s outside of Sentral and how to configure AMT settings for A1410s after deploying them in your environment. For more information, see "Provisioning AMT on Hosts" on this page. How to access AMT features on AMT hosts. For more information, see Using AMT in Your Sentral Environment on page 202. Provisioning AMT on Hosts The following sections describe how to provision AMT on a host so you can use the AMT features in the environment you manage with Sentral. You cannot use AMT features on a host until you provision AMT on the host. NOTE To perform the steps in the following sections you must remove the A1410 from the chassis and connect peripherals to the A1410. To provision AMT for a A1410, you must: 1. Enable AMT on the host. 2. Change the default administrator name and password. 3. If you are using Sentral to manage the A1410, ensure that the A1410 name is the same as the name assigned to the A1410 in Sentral. 4. Ensure that the network settings in AMT are specified appropriately. 5. Ensure that the correct provisioning mode is specified. 199

212 Enable AMT on the Host To enable AMT on a A1410: 1. Remove the A1410 from the chassis. 2. Attach a keyboard and monitor to the A1410 through the port access hole on the top of the A1410. Port Access Hole 3. Press the power button on the front of the A1410 and then press F2 at startup to enter the A1410 s BIOS. Power Button 4. Press the arrow keys to select the Intel (R) ME tab, and then press Enter. 5. Here you need to type the password to get access to the configuration functionality of AMT. Just type admin as your password string here for the first time only and press the Enter key. The default password for intel AMT is admin. As you will press the Enter key there pops an alert on your screen indicating you to use Save and Commit Settings option. Press Enter to continue and reset your AMT password. 6. Select the first highlighted option Management Engine Configuration from the same menu and press the Enter key. 200 ClearCube Technology, Inc.

213 Chapter 6: Using Intel Active Management Technology 7. Pressing the enter key will lead to the activation of Manageability Features option where you can choose the state of the AMT feature. You must select the Intel (R) AMT option by using the up/down direction keys from the keyboard and press Enter. 8. For the Turn On Intel ME in Sleep States value set to Always press down arrow key to choose from the options list as displayed in the screen below and press enter key to select the option. Press the Enter key to proceed. 9. Highlight the Save and Commit Settings option by using the Down Arrow key from keyboard and press enter. 10. Chose the Yes, submit the new settings option to commit and save the updated variable values. A confirmation message is displayed. 11. You must now reboot the system. Use Forward Arrow key from the keyboard to go to the exit Menu of setup. Select Exit Saving Changes and press Enter key from the keyboard. Press Y to exit and save your changes. Specifying Host Name in Sentral Perform the following steps: 1. After rebooting the A1410 as described in Enable AMT on the Host on page 200, press F2 to enter the A1410 BIOS. 2. Use the arrow keys to select the Intel(R) ME menu option and then press Enter. 3. Select Computer Name and then press Enter to display a text field in which you can type the A1410 s name. NOTE The A1410 name must be unique and must be the same name that is assigned to the A1410 in Sentral. Press Enter after typing the name to save your changes. Specifying the AMT Mode To manage your AMT host in Sentral, you must set AMT to Small-Medium Business mode. After specifying the network settings appropriate for your environment, perform the following steps from the A1410 BIOS. 1. Use your arrow keys to select the Intel(R) ME menu option, and then select Provisioning Configuration and press Enter. 2. Select Small-Medium Business and then press Enter. Sentral Administrator s Guide 201

214 3. Press the Esc key to return to the previous screen. 4. Select Save and Commit Settings and then press Enter. 5. Select Yes, submit the new settings and then press Enter. 6. Select the Exit menu option and then select Exit Saving Changes. Press Enter to exit BIOS. You can now deploy the A1410 in your Sentral environment and use the AMT features. See Using a Host s AMT Features on page 143 for information about using AMT features. Using AMT in Your Sentral Environment This section describes how to configure AMT settings for Sentral and how to perform AMT tasks from Sentral. Discovering AMT Hosts Perform the following steps to discover AMT hosts. AMT Hosts discovery is run by selecting the IP subnet range and clicking AMT Discovery. A new parameter has been added in the ServerConfiguration.xml file with the default value of one minute: <entry key="amt.discovery.timeout.value">1</entry> The discovery of the AMT hosts is more time taking because the AMT discovery keeps running at the back end while the Sentral is running in the front, that leads to the resource allocation for both the processes sustain till the discovery is complete. That is how the execution of Sentral gets quite inefficient for a while. 1. From the main menu, click Setup > Configuration, and then click AMT Discovery in the Tasks pane. 2. Type the AMT administrator user name and password in the dialog box and then click Submit. For information about specifying your AMT administrator, see Set AMT Administrator on page ClearCube Technology, Inc.

215 Chapter 6: Using Intel Active Management Technology After performing an AMT discovery, the discovered devices are displayed in the Management - AMT Hosts screen, as shown in the following figure. Figure 59. Management - AMT Hosts screen with discovered hosts Viewing Discovered AMT Hosts AMT host without host agent If a A1410 is AMT enabled but does not have the host agent installed, the MAC address of the A1410 does not appear in the Management - AMT Hosts screen as shown in the following figure. Figure 60. AMT host without host agent Multiple nodes with the same AMT hostname A single node appears in Sentral hierarchical tree (although multiple devices are displayed in the Discovered Devices Screen). Sentral Administrator s Guide 203

216 Performing AMT Tasks on Hosts See Using a Host s AMT Features on page 143 for instructions about the out-ofband tasks you can perform using a A1410 s AMT features. 204 ClearCube Technology, Inc.

217 Chapter 7: Connection Brokering Module Sentral utilizes the concepts of groups for the purpose of mapping, or allocating, resources. A group can contain one or more resources. Allocation defines the allowable connections (mappings) between the groups. For resources to interact, set up user, thin client, and host groups, and place these resources into their appropriate groups. Then establish the dynamic or static allocations between these groups. NOTE Virtual machine groups cannot be created or allocated, but a host group containing a host or host configured with virtual machines can be created. Virtual machines can then be allocated on a per-host basis in host groups. Mapping and Allocation Tasks Allocation consists of these tasks: Create groups Add resources to the groups Assign allocations between the connection and host or VM groups After they are created, allocations can be easily modified to allow for changing network needs and use. Three types of allocations are possible: Dedicated connects the user or thin client to the same assigned host or VM each time. Shared connects the user or thin client to any available host or VM in a shared host group, based on the least load average algorithm that Sentral uses to determine the best host or VM to assign to the user. Spare allows switching the user or thin client to any available spare blade (that is, a host) or VM in the event of a host or VM failure. Typically, spared hosts or VMs do not have any active connections. These hosts or VMs are, as the name suggests, reserved for use only when necessary as a replacement. More than one Spare Host Group can be created. 205

218 When a host or VM group is designated as a Dedicated group, users or thin clients can connect only to a specified host or VM in that group. This is a static mapping. It does not change between sessions. When a host or VM group is designated as a Shared group, users or thin clients can connect to any host or VM in the group, based on the least-load average algorithm, which monitors system usage characteristics and automatically assigns connections to the host or VM in the group that has the least load when the connection is attempted. This is a dynamic mapping in the sense that it may be different at the start of any given session. When a host or VM group is designated as a Spare group, users or thin clients can be re-mapped, or spared, to any available host or VM in that group, regardless of their allocation to a Dedicated or Shared host or VM group. For example, the thin clients in a thin client group named Sales thin clients could be configured to connect only to the hosts in a Host Group named Sales Hosts. When an end user logs in, the Sentral Console directs that user to a specific host, or to any host in a particular group, as allocated. The Connection Brokering Mappings screen presents a tabbed frame. The tab titles are Dedicated Allocations, Shared Allocations, and Spare Allocations. Within each of the tabbed frames are two multi-tabbed tables. The table on the left-hand side has two tabs marked Thin clients and Users. The table on the right-hand side has two tabs marked Hosts and Virtual Machines. Each allocation can be mapped four ways, so 12 allocation mappings are possible. These are: Dedicated Allocations Thin clients to Hosts Thin clients to Virtual Machines Users to Hosts Users to Virtual Machines Shared Allocations Thin clients to Hosts Thin clients to Virtual Machines Users to Hosts Users to Virtual Machines 206 ClearCube Technology, Inc.

219 Spare Allocations Thin clients to Hosts Thin clients to Virtual Machines Users to Hosts Users to Virtual Machines Chapter 7: Connection Brokering Module Dedicated Allocation Mapping Simple dedicated allocation mapping is useful in situations where a thin client or User is to be associated with a particular host or virtual machine (VM). Thin clients and users do not need to belong to any group in order to participate in a dedicated mapping. Even if a thin client or User is already participating in a shared mapping, it can still also participate in a dedicated mapping. On the other hand, hosts and VMs must belong to a dedicated group to participate in a dedicated mapping. Furthermore hosts and VMs in dedicated groups can not participate in any other form of allocation mapping. Complex dedicated allocation mappings can also be made. The rules for simple dedicated mapping still apply but multiple allocations are made between resources. A thin client or user can be mapped to multiple hosts or VMs. A single host or VM can be can be mapped to more than one thin client or user. Before going to complex dedicated mapping it may be better to try shared allocation mapping. Dedicated Mappings (Thin Clients to Hosts) Create a Dedicated Host Group by following these steps: 1. From the main menu, click on Connection Brokering > Groups. The Connection Brokering Groups screen is displayed. 2. In the Tasks menu, click on Manage Host Group. The Connection Brokering Host Groups (New) screen is displayed. 3. In the Tasks menu, click on New Group. The following table lists the host group parameters. Table 20. New Host Group Fields Field Name Group Name REQUIRED FIELD Description This field specifies the name of the Host Group, and a name must be entered. No more than 50 characters can be entered. Description Use this field to enter a description for the group. No more than 50 characters can be entered. Sentral Administrator s Guide 207

220 Table 20. New Host Group Fields (continued) Field Name Location Resource Type Description This pull-down menu specifies the group hierarchy, including the CCT group and all existing groups contained in CCT. Select the desired location within this hierarchy. This pull-down menu specifies the resource type for the group: Dedicated Select when assigning resources on a one-to-one basis Shared Select when resources may be shared Spare Select when resources are intended only for use as dedicated spare resources, such as a host or VM. The default selection is Dedicated. 4. In the lower portion of the screen, enter the Group Name and Description, select a location from the Location pull-down menu, and select Dedicated from the Resource Type pull-down menu. 5. Click on Add Group. The created group is displayed in the upper portion of the screen (and in the Hierarchical tree, if the Hierarchical view is selected). NOTE Groups are listed alphabetically. Next, create the mapping by following these steps: 6. Click on the Allocate Host group to Thin client group link in the lower portion of the screen. The Connection Brokering > Mappings screen is displayed. All the thin clients are listed in the Available Thin clients tab. In the Available Hosts tab, only those hosts for which the Host Group type is set to Dedicated are listed. See the following figure. 7. Select a thin client in the Available Thin client tab and a host from the Available Hosts tab. 8. Press Allocate. When a mapping is created, the Allocated to column displays the information about the allocation. Thin client displays the name of the allocated host, and Host displays the name of allocated thin client. Dedicated Mappings (Thin Clients to Virtual Machines) Create a Dedicated VM Group by following these steps: 1. From the main menu, click on Connection Brokering > Groups. The Connection Brokering Groups screen is displayed. 2. In the Tasks menu, click on Manage Virtual Machine Group. The Connection Brokering Virtual Machine Groups (New) screen is displayed. This group has 208 ClearCube Technology, Inc.

221 Chapter 7: Connection Brokering Module the same appearance and functionality as the Connection Brokering Host Groups (New) screen, except that it works with VM groups, not host groups. 3. In the Tasks menu, click on New Group. 4. In the New Host Group area in the lower portion of the screen, enter the Group Name and Description. 5. Select a location from the Location pull-down menu. This menu displays the CCT group (the default group) and all other groups created in the CCT group. 6. Select Dedicated from the Resource Type pull-down menu. 7. Click on Add Group. The created group is displayed in the upper portion of the screen (and in the Hierarchical tree, if the Hierarchical view is selected). NOTE Groups are listed alphabetically in the upper portion of the screen, not hierarchically. Create the mapping by performing the following steps: 8. Click on the Allocate this Virtual Machine group to a Thin Client group link in the lower portion of the screen. The Connection Brokering > Mappings screen is displayed. All the thin clients are listed in the Available Thin Clients tab. In the Available VMs tab, only those VM for which the VM Group type is set to Dedicated are listed. 9. Select a thin client in the Available Thin Clients tab and a VM from the Available VMs tab and press Allocate. When a mapping is created, the Allocated to column displays the information about the allocation. The thin client displays the name of the allocated VM, and VM displays the name of allocated thin client. Dedicated Mappings (Users to Hosts) Create a Dedicated Host Group (see Dedicated Mappings (Thin Clients to Hosts) on page 207), and then create a mapping by following these steps: 1. From the main menu, click on Connection Brokering > Mappings. The Connection Brokering Mappings screen is displayed. 2. Select the Dedicated Allocation tab and the Users tab. All the users are listed in the Available Users tab. 3. Select the Hosts tab. In the Available Hosts tab, only those hosts for which the Host Group type is set to Dedicated are listed. 4. Select a user in the Available Users tab and a host from the Available Hosts tab. Sentral Administrator s Guide 209

222 5. Click Allocate. When a mapping is created, the Allocated to column displays the information about the allocation. Users displays the name of the allocated host, and Host displays the name of allocated user. Dedicated Mappings (Users to Virtual Machines) Create a Dedicated VM Group (see Dedicated Mappings (Thin Clients to Virtual Machines) on page 208), and then create a mapping by following these steps: 1. From the main menu, click on Connection Brokerings > Mappings. The Connection Brokering Mappings screen is displayed. 2. Select the Dedicated Allocations tab and the Users tab. All the users are listed in the Available Users tab. 3. Select the Virtual Machines tab. In the Available VMS tab, only those VMs for which the VM Group type is set to Dedicated are listed. 4. All the users are listed in the Available Users tab. In the Available Hosts tab, only those hosts for which the Host Group type is set to Dedicated are listed. 5. Select a user in the Available Users tab and a VM from the Available VMS tab. 6. Press Allocate. When a mapping is created, the Allocated to column displays the information about the allocation. Users displays the name of the allocated VM, and VM displays the name of allocated user. Delete All Dedicated Allocation Mappings of a Thin Client or a User To delete all dedicated allocation mappings of a thin client or a user, perform the following steps: 1. From the main menu, click on Connection Brokerings > Mappings. The Connection Brokering Mappings screen is displayed. 2. Select the Dedicated Allocation tab. 3. Select the Thin Clients tab (or the Users tab). 4. Select one thin client (or user) to have its dedicated allocations deleted. 5. Click the Delete Current Allocation(s) button. 6. Click OK on the task completed dialog. 210 ClearCube Technology, Inc.

223 Chapter 7: Connection Brokering Module Note that the corresponding dedicated allocations for the thin client or user in the Hosts (or Virtual Machines) tab are cleared. Deleting dedicated allocations for Thin client Groups, Host Groups and VM Groups is similar. Shared Mapping Shared mappings are useful in situations where a group of thin clients or Users can use any one of a number of hosts or VMs. Shared mapping involves thin client and User groups in combination with shared Host and VM groups. The group allocation type (Dedicated, Shared, Spare) of the thin client and User groups is not relevant. The allocation type of the Host and VM groups must be Shared. In Sentral Version 5.8, you can now put VMs on one Host in separate groups. Creating Groups See Setting Up Security on page 97 for more information about applying security to groups you create. This section describes how to create a group for the following resources: Hosts Thin clients Users Virtual machines Domain groups In Sentral Console, you follow the same steps to create a Host, thin client, user, or virtual machine group. To create a group, perform the following steps. 1. From the main menu, click Connection Brokering > Groups. 2. Click one of the following links in the Task pane. Manage Host Group Manage Thin client Group Manage User Group Manage Virtual Machine Group Add Local/Domain Groups Sentral Administrator s Guide 211

224 3. The New Group screen appears in the lower portion of the screen. Click New Group in the Tasks menu and then perform the following steps: a. Type a name for the group in the Group Name field. b. Type a meaningful description of the group in the Description field. c. Select a location for the group in the Location drop-down box. d. Select an allocation type from the Resource Type drop-down box. For definitions of the allocations available, see Mapping and Allocation Tasks on page 205. e. Click Add Group. The new group is now displayed in the Hierarchical view. Mapping Domain and Local Security Groups Sentral Version 5.8 automatically discovers Active Directory security groups when you log in with a Domain account. As administrator, you must manually map the Active Directory group to a host group. In Sentral Version 5.8, Active Directory security groups are considered shared groups by default. Perform the following steps to map an Active Directory group to a host group. 1. From the main menu, click Connection Brokering > Mappings. 2. Click the Shared Allocation tab near the top of the upper portion of the screen. 3. Click the User Groups tab on the left-hand Select Target Group panel, and then select the Active Directory group you want to map to a host group. 4. Click the Host Groups tab on the in the right-hand Select Target Group panel, and then select the Host group to which you want to map the Active Directory Group. 5. Click the Allocate button at the bottom of the screen. A progress meter is displayed, and then a success dialog box is displayed. Click OK. 212 ClearCube Technology, Inc.

225 Chapter 7: Connection Brokering Module Sentral displays and highlights the newly-mapped groups in the Allocated to column in both of the Select Target Group Panes. Figure 61. Sentral highlights and displays mapped groups in the Allocated to column Adding Windows Security Groups To add an Active Directory group to Sentral, perform the following steps. NOTE You can perform the same steps to add a local group; however, change the configuration to discover Local groups rather than Domain groups. 1. Ensure that you have created an Active Directory group. 2. From the main menu, click Connection Brokering > Groups. 3. In the Tasks menu, click Add Local/Domain Groups to display the Connection Brokering - Groups (Add) screen. 4. Click a group in the Group Name column, and then click Add Selected Groups. The group or groups you selected are displayed in the Add group(s) screen in the lower portion of the screen. 5. For each group you are adding: a. Select Shared or Spare in the Group Type drop-down box b. Select the target group for the Active Directory group and then click Add. Sentral displays a confirmation dialog box; click OK to dismiss the dialog box. The Windows security group is now displayed in the Hierarchical view under the target group you specified in the previous step. Map a User Group to a Shared Virtual Machine Group 1. From the main menu, click on Connection Brokering > Mappings. The Connection Brokering Mappings screen is displayed. 2. Select the Shared Allocation tab. Sentral Administrator s Guide 213

226 3. Select the User Groups tab. 4. Select one User Group from the table of Target User Groups. 5. Select the VMS Groups tab. 6. Select one Virtual Machine Group from the table of Available VMS Groups. 7. Click the Allocate button. 8. Click OK on the task completed dialog. Note that the Allocated to field of the selected User group in the Available User Groups table and the selected VMS group in the Available VMS Groups table now refer to each other. To map a thin client group to a shared VMS group follow the instructions above but replace User with Thin client. To map a User group to a shared Host group follow the instructions above but replace VMS with Host To map a thin client group to a shared Host Group follow the instructions above but replace User with thin client and VMS with Host. Delete All Shared Allocation Mappings for a User To delete all shared allocation mappings for a user, perform the following steps: 1. From the main menu, click on Connection Brokerings > Mappings. The Connection Brokering Mappings screen is displayed. 2. Select the Shared Allocation tab. 3. Select the User Groups tab. 4. Select one User group. 5. Click the Delete Current Allocation(s) button. 6. Click OK on the task completed dialog. Note that the selected User group's corresponding shared allocations are cleared in the Available Host Groups table and/or Available VMS Groups table. Deleting shared allocations for Thin client Groups, Host Groups and VM Groups is similar. 214 ClearCube Technology, Inc.

227 Chapter 7: Connection Brokering Module Spare Mapping Spare allocation mapping is useful when a host or VM needs to be taken offline and the current thin clients and Users need to be moved to some other host or VM. Spare mapping involves thin client and User groups in combination with host and VM groups. The group allocation type (Dedicated, Shared, Spare) of the thin client and User Group is not relevant. The allocation type of the host and VM Groups must be Spare. Map a Thin client Group to a Spare Host Group To map a thin client group to a spare host group, perform the following steps: 1. From the main menu, click on Connection Brokerings > Mappings. The Connection Brokering Mappings screen is displayed. 2. Select the Spare Allocation tab. 3. Select the Thin client Groups tab. 4. Select one thin client Group from the table of Available thin client Groups. 5. Select the Host Groups tab. 6. Select one Host Group from the table of Available Host Groups. 7. Click the Allocate button. 8. Click OK on the task completed dialog. Note that the Spare Alloc. field of the selected thin client group in the Available thin clients table and of the selected Host group in the Available Hosts table now refer to each other. To map a thin client group to a spare VM group, follow the previous instructions but replace Host with Virtual Machine. To map a User group to a spare Host group, follow the previous instructions but replace thin client with User. To map a User group to a spare VM group, follow the previous instructions but replace thin client with User and replace Host with VM. Delete All Spare Allocation Mappings of a Host Group To delete all spare allocation mappings of a host group, perform the following steps: Sentral Administrator s Guide 215

228 1. From the main menu, click on Connection Brokerings > Mappings. The Connection Brokering Mappings screen is displayed. 2. Select the Spare Allocation tab. 3. Select the Host Groups tab. 4. Select a Host Group in the Available Host Groups Table. 5. Click the Delete Current Allocation(s) button. 6. Click OK on the task completed dialog. Note that the corresponding spare allocations to the selected Host group in the thin client Groups and/or VM Groups table are also cleared. Deleting spare allocations for thin client Groups, User Groups, and VM groups is similar. 216 ClearCube Technology, Inc.

229 Chapter 8: Switching Module The Switching Module is the Sentral module that allows you to manage the centralized components of a ClearCube hardware infrastructure. The Sentral Switching Module offers a graphical view of the ClearCube chassis. From this view, you can monitor out-of-band readings of ClearCube blade (host) and chassis temperatures, voltages, and fan speeds. The Sentral Console allows you to shut down and restart blades remotely, but only the Switching Module allows you to perform a hard reset of blades (out-of-band). A hard reset produces the same result as physically pushing the reset button on the front of the blade. This type of reset is required when the operating system locks up or when the blade becomes otherwise unresponsive. The Sentral Switching Module offers Spare Switching, 8x8 Switching, and Admin Switching. Using Spare Switching, the administrator can switch any user to a hot spare. Using 8x8 Switching, an administrator can switch any C/Port to any blade within a chassis. Using the Admin Switching functions, an administrator can monitor the desktop of any blade in use, or take hardware control of any blade. The hardware remote control feature means administrators can take control of a blade regardless of the operating system type or status, and even re-image a blade remotely. Available Switching Module Modes The following modes of operation are provided in the Sentral Switching Module: Manage Spare Switching 8x8 Switching Supervisor View Supervisor Control Admin/KVM Switch Subsequent sections in this manual provide detailed explanations of these modes, along with information on using the modes. 217

230 Manage The Manage Mode is the default mode that the administrator sees when logging in to Switch Manager. In this mode, the administrator can select different C/Ports or blades to view their information or rename them. Spare Switching The Spare Switching Mode lets an administrator remotely switch a user from their primary blade to a designated spare blade. An IT technician can then work on the problem computer while the end user continues working on a spare. This can dramatically reduce downtime, since the end user does not need to wait for desk side support. Because multiple chassis can be daisy-chained together, a single spare blade can be made available to multiple blades in multiple chassis. NOTE For Spare switching to work, a Spare blade must be correctly cabled to the chassis. See Figure 84 on page 287, Figure 85 on page 288, and Figure 86 on page x8 Switching The 8x8 Switching Mode lets the administrator connect any C/Port to any blade within the same chassis. This capability also lets one or more users share multiple blades dynamically. For example, one user can switch among multiple computers that are simultaneously performing different tasks. Supervisor View The Supervisor View Mode allows the administrator to share the screen video with an end user located elsewhere in the facility. This feature is useful for training, collaborative troubleshooting, and performance monitoring. To accomplish this, the user's monitor signal is routed to both the end user's and the supervisor's monitors. This feature is completely independent of any software that may be running on the end user's computer, and works even if the end user s operating system is locked up. Supervisor Control The Supervisor Control Mode allows the administrator to gain control over the keyboard and the mouse of a user s blade while sharing his screen video. This feature is very useful for visually showing the user how to perform certain actions. The user can see the administrator move the mouse and type on the keyboard. This is very useful for training, collaborative troubleshooting, and performance monitoring. 218 ClearCube Technology, Inc.

231 Chapter 8: Switching Module Admin/KVM The Admin/KVM Switch mode gives full control of the user s blade to the administrator. In this mode, the administrator switches the user s keyboard, mouse, and video over to himself to be able to work on the blade. This completely eliminates sending an IT technician to the user s location. The administrator can switch the user to a spare blade while remotely working on the user s primary blade. NOTE This mode completely disconnects the user by removing video and the digital link from their blade while the administrator takes full control. Switching Operations C/Port Switching allows switching C/Port users between blades within an R4200 Blade Switching BackPack (BSBP) or an R4300 chassis. Since C/Ports are hard-wired through the switch matrix in the chassis, switching is limited to the blades installed within a chassis. You cannot switch C/Ports between blades in different chassis. The Switching C/Ports screen can be accessed in two different ways: From the Hierarchical view by left-clicking on a chassis icon. From the main menu by following this procedure. 1. From the main menu, select Switching > C/Ports. The Switching C/Ports screen is displayed. See Figure 62 on page 219. Figure 62. C/Port switching screen and chassis selection dialog box 2. Click on a row in the upper portion of the screen. The Select BackPack dialog box is displayed (see the following figure). 3. Select a BackPack with the pull-down menu and click OK. A confirmation dialog box is displayed. Select Continue in the next dialog box to proceed to the Sentral Administrator s Guide 219

232 graphical Switching C/Ports screen that represents the chassis you selected. See the following figure. Figure 63. Graphical C/Port Switching Screen Switching C/Ports between Blades To use the graphical Switching C/Ports screen, perform the following steps: 1. From the Switching Mode pull-down menu, select a switching mode. Options include: Manage Allows only management tasks on individual blades Spare Allows switching a C/Port to the attached spare blade 8x8 Switch Allows switching C/Ports between blades within the displayed chassis 220 ClearCube Technology, Inc.

233 Chapter 8: Switching Module Supervisor View Allows an administrator to view the video on a user s blade Supervisor Control Allows an administrator to view the video on a user s blade, and share keyboard and mouse control of that blade Admin/KVM Gives an administrator complete control of the blade, and disconnects the user s video and digital link 2. To use Manage mode, perform the following steps: a. Select Manage mode and click on a blade. The Blade Operations Dialog is displayed, as shown in the following figure. Figure 64. Host Operations Dialog Box b. Do one of the following: Click Rename LCD to change the text displayed on the blade front-panel LCD. You can enter as many as 10 alpha-numeric characters, spaces, or the caret ( ^ ) character. Non-alphanumeric characters are displayed as spaces, and lower-case alphabetical characters are displayed as uppercase. Entering the caret turns on all the LCD segments. Click Blink LCD to flash the blade front-panel LCD on and off. Click Unblink to stop flashing the blade front-panel LCD. Click BPIC Version to display the blade BPIC software version. Click Reset Blade Power to cycle power on the blade. These options are available in all of the Switching modes. Notice that the background changes to a pink color. 3. To use Spare mode, perform the following steps: a. From the Switching Mode pull-down menu, select Spare mode. Notice that the background of the Switching C/Ports screen turns pink to indicate Spare mode. See Figure 65 on page 222. b. Click the radio button above the C/Port that you wish to switch to the spare blade. A confirmation dialog is displayed. Sentral Administrator s Guide 221

234 c. Click the Un-Spare link to un-spare the C/Port. A confirmation dialog is displayed. Un-Spare link Switch Button Figure 65. Spare Switching Mode Screen 4. To use 8x8 Switch mode, perform the following steps: a. From the Switching Mode pull-down menu, select 8x8 Switch mode. Notice that the background of the Switching C/Ports screen turns a light blue color to indicate 8x8 Switching mode. See Figure 66 on page 223. b. Click the radio button above the C/Port that you wish to switch to another blade, and click the Switch button. A confirmation dialog is displayed. After you confirm the switch, the Switch Icon is displayed above the blade that has been switched to the new C/Port and the link line between the blade and the original C/Port is gone. c. To switch back, click the radio button above the original C/Port (the radio button below this blade is selected), and click the Switch button. A confirmation dialog is displayed. After you confirm the switch, the Switch 222 ClearCube Technology, Inc.

235 Chapter 8: Switching Module Icon is gone, and the link line between the blade and the original C/Port is restored. Switch Icon Switch Button Figure 66. 8x8 Switching Mode Screen 5. To use Supervisor View mode, perform the following steps: a. From the Switching Mode pull-down menu, select Supervisor mode. Notice that the background of the Switching C/Ports screen turns a light yellow color to indicate that an Admin mode has been selected. See Figure 67 on page 224. b. Click the radio button above the C/Port that you wish to switch to another blade, and click the Switch button. A confirmation dialog is displayed. After you confirm the switch, the Switch Icon is displayed above the blade that has been switched to the new C/Port and the link line between the blade and the original C/Port is gone. c. To switch back, click the radio button above the original C/Port (the radio button below this blade is selected), and click the Detach Admin link. A confirmation dialog is displayed. After you confirm the switch, the Switch Sentral Administrator s Guide 223

236 Icon is gone, and the link line between the blade and the original C/Port is restored. Detach Admin link Switch Icon Switch Button Figure 67. Supervisor View Mode Screen 6. To use Supervisor Control mode, perform the following steps: a. From the Switching Mode pull-down menu, select Supervisor Control mode. Notice that the background of the Switching C/Ports screen turns a light yellow color to indicate that an Admin mode has been selected. See Figure 68 on page 225. b. Click the radio button above the C/Port that you wish to switch to another blade, and click the Switch button. A confirmation dialog is displayed. After you confirm the switch, the Switch Icon is displayed above the blade that has been switched to the new C/Port and the link line between the blade and the original C/Port is gone. c. To switch back, click the radio button above the original C/Port (the radio button below this blade is selected), and click the Detach Admin link. A confirmation dialog is displayed. After you confirm the switch, the Switch 224 ClearCube Technology, Inc.

237 Chapter 8: Switching Module Icon is gone, and the link line between the blade and the original C/Port is restored. Detach Admin link Switch Icon Switch Button Figure 68. Supervisor Control Mode Screen 7. To use Admin/KVM mode, perform the following steps: a. From the Switching Mode pull-down menu, select Admin/KVM mode. Notice that the background of the Switching C/Ports screen turns a light yellow color to indicate that an Admin mode has been selected. See Figure 69 on page 226. b. Click the radio button above the C/Port that you wish to control, and click the Switch button. A confirmation dialog is displayed. After you confirm the switch, the Switch Icon is displayed above the blade that you now control, and the link line between the blade and the original C/Port is gone. c. To switch back, click the radio button above the original C/Port (the radio button below this blade is selected), and click the Detach Admin link. A confirmation dialog is displayed. After you confirm the switch, the Switch Sentral Administrator s Guide 225

238 Icon is gone, and the link line between the blade and the original C/Port is restored. Detach Admin link Switch Icon Switch Button Figure 69. Admin/KVM Mode Screen NOTE When a C/Port has been switched to the Spare Blade port or to the Admin Port, the Management C/Ports screen lists the C/Port s Slot number as -1. See Figure 70 on page 227 for more information. 226 ClearCube Technology, Inc.

239 Chapter 8: Switching Module Figure 70. Management C/Ports Screen Switching Thin Clients Between Blades or VMs Since thin clients connect via Ethernet and the Sentral Client, they can be allocated and connected at any distance to any blade or VM that uses Ethernet. To switch between thin clients and blades or VMs, perform the following steps: 1. From the main menu, select Switching > Thin clients. The Switching Thin clients screen is displayed. See Figure 71 on page Select the Thin clients tab or the Users tab from the left side of the upper portion of the screen. 3. In the Available Thin clients pane (or the Available Users pane, if chosen), click the thin client (or user) to which you wish to switch. The row for this thin client is highlighted. Sentral Administrator s Guide 227

240 4. Select the Blades tab or the VMs tab from the right side of the upper portion of the screen. Figure 71. Thin client Switching Screen 5. In the Available Blades pane (or the Available Virtual Machines pane, if chosen), click the blade (or VM) to which thin client or user should be switched. The row for this resource is highlighted. 6. At the bottom of the upper portion of the screen, click the Switch button. A confirmation dialog box is displayed. 7. Click the Yes button to confirm the switch. 8. If the blade is not currently in use, the switch is completed and a dialog box confirming the successful switch is displayed. 9. If the blade is in use, a second confirmation box is displayed. 10. Click Yes to perform the switch, or click No to cancel. 228 ClearCube Technology, Inc.

241 Chapter 8: Switching Module Switching Users Between Blades or VMs The procedure for switching users between blades or VMs is identical to the procedure for switching thin clients between blades or VMs except that the Users tab is selected from the upper portion of the screen, as noted in the previous procedure. From the main menu, select Switching > Users. The Switching Users screen is displayed. Sentral Administrator s Guide 229

242 230 ClearCube Technology, Inc.

243 Chapter 9: Tasks Hierarchical View An alternate method of managing your assets with Sentral is to use the Hierarchical Tree Menu, select the Hierarchical Tab, in the left hand menu pane. With the Hierarchical view, the Administrator can see all the assets managed by Sentral. Each asset or group of assets is represented iconically on the Hierarchical view. Icons in the Hierarchical view can be managed by either left clicking (to access immediate functions) or right clicking (to access additional functions). When right clicking on the icons, all additional options available for that asset are displayed and may be selected. Each selection displays the appropriate screens. This section discusses each asset and options available to that asset. The Administrator can also use drag and drop techniques on the Hierarchical view. For example, it is very efficient to move a user from the default group, CCT, into a different selected group using drag and drop. Table 5 on page 69 shows the icons used on the Hierarchical view. An icon containing an X represents a node that has not reported back to the Sentral Console in the configured timeout time. These nodes are considered to be offline. Sentral Node The top node of the Hierarchical view is the Sentral node. This node cannot be removed. Sentral is represented by the Group Icon. Left-clicking on the Sentral node does not result in any action. Double-clicking the group icon or the word Sentral results in expanding or collapsing the Hierarchical view. Right-clicking on the Sentral node brings up a menu with one option: Refresh This selection updates the entire Hierarchical view and associated screens. The larger the total number of assets, the longer that refresh will take. If you make a hardware change to your Sentral network (such as inserting or removing a host), you need to select Refresh in this fashion to make the hardware change visible. In addition, if an RMM failover occurs, you need to refresh the Hierarchical view to correctly display the failover. NOTE Clicking the Refresh button at the top of the screen does not refresh the Hierarchical view. 231

244 CCT Node This is the base node and holds all the assets that are discovered, automatically inventoried, or created by the administrator. This name, CCT, cannot be edited or deleted. The CCT node holds all the listed items including all default items created or discovered until they are moved by the administrator. Left-clicking on the CCT node does not result in any action. Double-clicking the group icon or the letters CCT results in expanding or collapsing the Hierarchical view. Right-clicking on the CCT node brings up a menu with the following option: Add Group This selection pops up an Add Group dialog box that allows the Administrator to create a Group Name, Description and Resource Type: Dedicated, Shared, or Spare. The Name field is a required field. NOTE Special characters are allowed in the Group Name/Description. Group Nodes These nodes represent a collection of items. Group do not have to be homogenous, and may contain hosts, users, chassis, VMs, etc. Operations allowed on groups are Add Group, Modify Group, and Delete Group. In some cases, the ability to group assets allows actions to be taken on the entire group. You can move multiple nodes from one group to another using Ctrl-Click or Shift- Click. When you move nodes from one group to another, the nodes inherit the resource type properties (dedicated, shared, or spare) of the target node. For more information about resource types, see Table 21 on page 233. Double-clicking the group icon expands or collapses all sub-tree components in that group. 232 ClearCube Technology, Inc.

245 Chapter 9: Tasks Hierarchical View Right-clicking a group node brings up a menu with three options, as shown in the following figure. Figure 72. Group node right-click options from Hierarchical view The following list and table describes each right-click menu option. Add Group This selection pops up an Add Group dialog box that allows the Administrator to create a Group Name, Description and Resource Type: Dedicated, Shared, or Spared. The following table lists the group configuration fields for adding or modifying a group. Table 21. Group Configuration Fields Field Name Group Name REQUIRED FIELD Description Resource Type Description This field specifies the name of the Chassis Group, and a name must be entered. Special characters are allowed in this field. The default is CCT\. This is a user-definable field. Special characters are not allowed in this field. The default value is empty. This pull-down menu specifies the resource type for the group: Dedicated Select when assigning resources on a one-to-one basis Shared Select when resources may be shared Spare Select when resources are intended only for use as dedicated spare resources, such as a host or VM. The default selection is Dedicated. Sentral Administrator s Guide 233

246 Modify Group This selection pops up a Modify Group dialog box that allows the Administrator to update the Group Name and Description. The Administrator can also update the group Resource Type: Dedicated, Shared, or Spare. Delete Group This selection allows deleting the group. You are asked for confirmation and a confirmation dialog box is displayed after successful deletion. It is important to note that deleting a group removes all its attributes from Sentral Console and the Sentral database. Chassis Group Nodes The Chassis Group is the name given to a Primary chassis and any other chassis that are managed by the RMM or RMC in that Primary chassis. It is recommended to have only RMMs as chassis management modules. More functions are available when using a RMM in a R4300 model chassis as the chassis management module. The Chassis Group can consist of the one Primary chassis or may have as many as 13 additional chassis in its Chassis Group. The Chassis Group icon may expand from one to 14 total chassis icons. The first blue chassis icon in any Chassis Group represents the Primary chassis with the Primary RMM. The second blue icon represents the Secondary chassis with the Secondary RMM. The chassis in the Chassis Group can be homogenous in type or mixed R4200 and R4300 chassis. For a brief explanation of Admin and Spare Cabling please see Admin and Spare Daisy Chains on page 284. For detailed feature and function lists for all types of chassis please see the R Series User s Guide, available on the ClearCube support site. Left-clicking on a Chassis Group node does not result in any action. Double-clicking the Chassis Group icon or the Chassis Group name results in expanding or collapsing of all sub-tree components under that Chassis Group. 234 ClearCube Technology, Inc.

247 Chapter 9: Tasks Hierarchical View Right-clicking a chassis group node brings up a menu with three options, as shown in the following figure. Configure This selection brings up the Management Configure Chassis screen. This screen provides information for the Primary chassis. See Configuring Chassis on page 120 for complete procedures on configuring a chassis. NOTE Only R4300 chassis can be configured with Sentral. To configure an R4200, use telnet. View Health & Status This selection brings up the Health and Status Chassis screen with all the Chassis Groups in CCT and the selected Chassis Group highlighted In the lower portion of the screen. For more information, see Health & Status Chassis on page 177. Delete Node This selection deletes the chosen node. A confirmation dialog box is provided. If the node is deleted, all assets contained in the node are removed from the Sentral database. The physical assets will be restored on the next Discovery, but any group or allocation information is permanently discarded, and needs to be restored manually. Sentral Administrator s Guide 235

248 Chassis Nodes The chassis icon represents a ClearCube chassis. These icons represent: A3100 model chassis R4200 model chassis R4300 model chassis A3100 Chassis This section describes tasks related to the A3100 chassis. Configuring the Chassis View Refresh Rate The ServerConfiguration.xml file contains a refresh rate tag that specifies the A3100 chassis view refresh rate, in seconds: <entry key="bmc.chassis.refresh.time.seconds">5</entry> The default value for refresh time is 5 seconds. The A3100 chassis view automatically refreshes after the specified duration. If a blade has been moved from one slot to another, the chassis view is updated accordingly. The ServerConfiguration.xml file is located in the following directory: C:\Program Files\Apache Group\Tomcat 4.1\ webapps\cmsserver\web-inf\configuration\properties 236 ClearCube Technology, Inc.

249 Chapter 9: Tasks Hierarchical View Monitoring Blades in Chassis From the Hierarchical view, click a BMC icon to view chassis and blade health and status information. Figure 73. A3100 Chassis Management screen Select a blade in the Blade # drop-down box to see any of the following health and status data about that blade. Voltage Fan status Red fan is off Green fan is on BMC firmware version Sentral Administrator s Guide 237

250 Changing a Chassis Name or Alias To change a chassis name: 1. Click the chassis Backpack Alias link at the top of the Management - A3100 Chassis screen. 2. Type a new name in the text field and click OK. Changing a Blade Alias To change a blade name: 1. Right-click the blade in the Hierarchical view and select Rename Blade. 2. Type a new name in the text field and click OK, as shown in the following figure. The name is updated in the hierarchical view and in the A3100 chassis view. Managing Blades in the Chassis View The following sections describe blade specific tasks you can perform from the Management - A3100 Chassis screen: Rename LCD Blink LCD and unblink LCD System Power Off OS Shutdown Clicking a blade in the Management A3100 Chassis view displays this the dialog box shown in the following figure. 238 ClearCube Technology, Inc.

251 Chapter 9: Tasks Hierarchical View Rename LCD From this pop up you can choose to rename the LCD for the selected blade and click the OK command button to commit the change or click Cancel command button to abort the operation. This value is displayed temporarily as there is limitation so far to fetch and display the value from the blade LCD so whenever the chassis view is refreshed or the focus from the selected blade changes the LCD displayed value goes blank. That is because the value which is displayed has been set by using a command both on the LCD chassis view and on the blade as well and not actually fetched from the blade machine. More over if an A1410 LCD is set to blink and its power has been reset, the LCD will stop blinking each time whenever the power has been reset. Blink LCD Selecting this operation will cause the LCD to blink on the hardware end only and there will be no indication on the screen for this operation. Unblink Selecting this operation will cause the LCD to stop the blinking on the hardware end only and there will be no indication on the screen for this operation as well. System Power Off The following figure shows the dialog box displayed after clicking System Power-Off. Click Yes to power off the system. Click No to cancel the operation. Sentral Administrator s Guide 239

252 OS Shutdown The following figure shows the dialog box displayed after clicking OS Shutdown. Click Yes to shut down the operating system. Click No to cancel the operation. R4200 and R4300 Chassis The R4200 model chassis support the RMC management module, while the R4300 model chassis require the RMM management model. There is only one Remote Management Module needed for each Chassis Group. This icon will be either blue, designating either a Primary or Secondary chassis, or black. Left-clicking on a chassis icon or the chassis serial number results in different actions according to the state and number of clicks. Single-clicking on the chassis icon or chassis serial number have two possible actions: The first left-click on the chassis icon or chassis serial number causes the Switching C/Ports screen to be displayed. For more details, see Switching Operations on page 219. A subsequent single left-click on the chassis icon or chassis serial number refreshes this screen. Double-clicking the left mouse button on the Chassis Group icon or the Chassis Group name expands all the sub-tree components under that chassis. These sub-tree components are the blade serial numbers located within that chassis. Left-clicking on a blade serial number pops up an Input Dialogue Box that allows the Administrator to rename that blade. NOTE Special characters are not allowed in the blade name. To collapse the chassis icon tree, left-click on the located in front of the chassis icon. Right-clicking on chassis icon or the chassis serial number brings up a menu with one option: 240 ClearCube Technology, Inc.

253 Chapter 9: Tasks Hierarchical View Configure This selection brings up the Management Configure Chassis screen. This screen provides information for the Primary chassis. See Configuring Chassis on page 120 for complete procedures on configuring a chassis. Host Nodes The host icon represents a host (that is, a physical computer, blade, VM, or other computing device with running a host agent). Right-clicking the host icon or the host name brings up a pop-up window with these options, all of which are accessible through the main menu. Configure View Health & Status Map Host to Thin client Remote Control Delete Node Wake on LAN Restart Shutdown This provides a convenient shortcut to those tasks. NOTE For a host represented by a serial number within a chassis submenu, the Administrator can access all these functions from the Switching C/Ports screen. Switching C/Ports between Blades on page 220. Sentral Administrator s Guide 241

254 The following figure shows the host right-click menu. Figure 74. Host right-click menu options Configure: Brings up a screen with a list of all the hosts. Select the host you wish to configure. This choice brings up the Management Configure Hosts. View Health & Status: Allows you to view the health and status for a host. This choice brings up the Health and Status Hosts screen, as shown in Health & Status Hosts on page 182. Advanced PCoIP Configuration Map Host to Thin Client: Allows you to map a host to a thin client. This choice brings up the Connection Brokering Mappings screen. Remote Control: Allows you to assume remote control of the selected host. 242 ClearCube Technology, Inc.

255 Chapter 9: Tasks Hierarchical View Delete Node: Enables you to select a node from Hierarchical view and delete it. NOTE You must shut down a node before you can permanently remove it. If you select Delete Node before you shut down the node, the Host Poll Time value can cause the host to poll the server and reappear in the Hierarchical view. This does not occur if you shut down a node before you delete it. Wake on LAN Restart: Allows you to restart the selected host. Shutdown: Allows you to shut down the selected host. In addition, the Hierarchical view allows you can move nodes from group to group, by drag-and drop operations. Any type of node can be dropped into any type of group, regardless of the rules imposed in the main menu. Sentral Administrator s Guide 243

256 244 ClearCube Technology, Inc.

257 Chapter 10: Host Agent Tasks The Asset Management screen, which is the main screen in the Sentral Host Agent, is shown in the following figure. Figure 75. Sentral Host Agent Main Screen The following table describes the host agent menu options, located in the left portion of the screen. Table 22. Host Agent System Management Menu Options Field Name Asset Management Drives Description This menu option provides basic system asset management information such as machine name, domain, and serial number. This menu option provides basic information about the hard drives and partitions installed on this system. 245

258 Table 22. Host Agent System Management Menu Options (continued) Installed Applications Keyboard/Mouse Memory Motherboard Multimedia Network Operating System I/O Ports Processor System Resources Video BIOS Field Name Description This menu option provides a list of the applications installed under Windows on this system. This menu option provides basic information about the keyboard and mouse installed on this system. This menu option provides basic information about the memory installed on this system. This menu option provides basic information about the main system board installed in this system. This menu option provides basic information about multi-media drivers installed on this system. This menu option provides basic information about the network connections active on this system. This menu option provides basic information about the operating system, a list of running processes, a list of defined Environment variables and their values, and a list of installed system drivers. This menu option provides basic information about the I/O ports on this system. This menu option provides basic information about the processor installed in this system. This menu option provides basic information about the system resources, including IRQ settings, DMA settings, I/O port settings, and memory mapping. This menu option lists all the available video settings for this system. This menu option provides basic information about the system BIOS. These menu options provide an easy method to view system information, but provide no means to actually edit the information. Although you can type over the entries in the information screens accessible in the host agent, none of your changes can be saved. The Sentral host agent uses the following keyboard shortcuts: Ctrl-P Alert Configuration Ctrl-S Exit Client Ctrl-X About the Sentral host agent 246 ClearCube Technology, Inc.

259 Chapter 10: Host Agent Tasks Configure the Host Agent at the Client The following figure shows the Host Agent configuration screen. Figure 76. Host Agent Configuration Screen Sentral Administrator s Guide 247

260 Perform the following steps to configure the host agent. 1. From the Sentral host agent window, click File > Configuration to display the Configuration screen. 2. Edit the fields as appropriate for your environment, as described in the following table. Table 23. Host Agent Configuration Fields Field Name Primary Server Secondary Server Description This field specifies the Primary Sentral Server. This field specifies the Secondary Sentral Server. Server Port The default value is Glue Server Port The default value is Alert Evaluation Time (min.) This field specifies the time interval for evaluating an Alert. The default value is 30 minutes. A timer is started the first time an Alert is sent. When the time specified in this field elapses, the Alert is re-evaluated. Alert Firing Time (hrs) Host Poll Time (min) This field specifies the time interval after which an Alert is fired. The default value is 1 hour. This field specifies the time after which a host reports back to the server with a heartbeat, in minutes. This value should be less than the Host Refresh Time. The default value is minutes. 248 ClearCube Technology, Inc.

261 Chapter 10: Host Agent Tasks Table 23. Host Agent Configuration Fields (continued) Field Name Domain Type Local Security Groups Domain Security Groups Description This pull-down menu provides the basis for user authentication. Choices include: AD (Active Directory) NT (NT 4) The default selection is AD. This pull-down menu lists the Security Groups defined on the machine. Pull-down menu. Choices include the Domain Groups defined by the Domain Manager for the Domain. 3. Click Save to save the configurations, or Cancel to discard them. Update the Host Agent from the Client 1. Update files must be present on the FTP Server system in the following folder: C:\Program Files\ClearCube Sentral\FTPServer\BladeUpdate 2. Select the Update Me button located near the top right of the screen in the ClearCube Sentral Host Agent window. When the update is completed, a dialog box is displayed that confirm the files were copied. If the update is not successful, a dialog box stating Files cannot be copied is displayed. If this occurs, verify that the FTP Server is running and that the files are in the correct update folder. Configure Host Agent SNMP 1. From the Sentral Host Agent window, select File > SNMP. The SNMP Configuration screen is displayed. 2. Edit the parameters in shown in the following table as they apply to your environment. Table 24. Host SNMP Configuration Fields Field Name Description Port Trap Receiver This field specifies the UDP port to which traps are sent. The default is 162, and should not be changed unless you open this port across the network to your trap receiver system, and configure the receiver to accept SNMP traps on this port. This field specifies the system that receives the SNMP traps sent. The default value is localhost, and should be changed to the hostname or the IP address of the trap receiver system. Sentral Administrator s Guide 249

262 Table 24. Host SNMP Configuration Fields (continued) Field Name Community String Enterprise Trap Sender Generic Trap Specific Trap OID Type of Trap Format Description This field specifies the SNMP community name used in traps sent to this destination. The default value is public. This field specifies the object identifier that uniquely identifies the Enterprise ID in the MIB. The default value is This field specifies the system where the SNMP agent that sends trap notifications to the host and port that you specify. The default value is localhost, and should be changed to the hostname or the IP address of the trap sender system if it is different from this Sentral console. This field indicates that the trap is enterprise-specific. SNMP vendors and users define their own traps under the privateenterprise branch of the SMI object tree. The default value is 6. This field specifies the enterprise-specific trap number, and applies only when the Generic Trap = 6. To process this trap properly, the NMS has to decode the specific trap number that is part of the SNMP message. The default value is This field specifies the SNMP Object Identifier (OID). The default value is This field specifies the type of trap format. The default value is String. 3. Click Save to save the changes, or click Cancel to discard them. Configure Alerts on the Host Agent 1. From the Sentral Host Agent window, select Notification > Alert Configuration. The Alert Configuration screen is displayed. 2. Click an item in the Monitor column, once one item is selected in the Monitor Panel, the focus moves to the Evaluate column. 3. Click an item in the Evaluate column that matches your required operator. After selection, the focus moves to the Action column. 4. Click the desired action in the Action column. A confirmation window is displayed. 5. Enter a name for the Alert. 6. Click SNMP if desired. SNMP is optional. 7. Click Save. A confirmation window is displayed, and the new Alert data is mapped into the Configured Alerts lower portion of the screen. 250 ClearCube Technology, Inc.

263 Chapter 10: Host Agent Tasks Notes Alerts are deployed as soon as they are configured and saved on the host agent. If you want to cause multiple actions to occur, you can select several items before saving the Alert. If you want to specify several Evaluate conditions, then you have to select a Monitor value and an Evaluate value for each of the extra conditions. You cannot check for a condition of Memory >= 100 MB and <= 200 MB. Instead, you would need to establish a separate entry for each condition, as Memory >= 100 MB and Memory <= 200 MB. The conditions must all test true for the Alert to fire. To set an either/or condition, deploy distinct Alerts, one for each condition. Then when any of the conditions evaluates to True, the corresponding Alert is fired. With one exception, all the Evaluate values are numeric, and can include decimal places. For Installed Applications, the field is a string, whose value must (except for upper/lower case) exactly match the name of the software application, as found in the Control Panel, under Add/Remove Programs. Since the Actions include Restart/Shutdown, you may want to have a DOS window open and handy. When the Alert fires, it triggers a shutdown, and you may not want to actually go through the process. To avoid the actual shutdown, wait for the notification that a shutdown is in progress. You then have 30 seconds (configurable to other values) to activate the DOS window and execute the shutdown a command to abort the shutdown. Edit Alerts on the Host Agent 1. From the Sentral Host Agent window, select Notification > Alert Configuration. The Alert Configuration screen is displayed, with all the deployed Alerts displayed in the lower portion of the screen. 2. Select an item in the table of configured Alerts. 3. Click the Edit Alert button in the Alert Tasks menu. 4. Use Add Item to add another value from the currently highlighted panel. Use Remove Item to delete the currently highlighted item. Notes: 1. Only one Alert can be edited at a time. 2. The current element's value is highlighted in the selection panels. If you want to change a different element, use the Next Item or Previous Item buttons to navigate to the item you wish to change. Sentral Administrator s Guide 251

264 3. The Configured Alerts table in the Secondary shows a truncated version of the Alert's settings. If the Alert is selected and you hover the mouse over it, the complete configuration list is displayed for several seconds. 4. Changes to Alerts may not cause the Alert to fire immediately. The values are not checked until the firing interval has elapsed. Delete Alerts on the Host Agent 1. From the Sentral host agent window, select Notification > Alert Configuration. The Alert Configuration screen is displayed. 2. Click an item in the table of configured Alerts. The item will be highlighted. 3. Click Delete. A confirmation dialog is displayed, indicating that the Alert has been deleted. The entry is removed from the table. Log Off the Host Agent To log off the host agent, select File > Log Off or File > Exit. from the Sentral host agent window. 252 ClearCube Technology, Inc.

265 Chapter 11: Thin Client and Thin Client Agent The thin client and thin client agent enable host users and Sentral administrators to: Log in to a host. See Logging in to a Host from a Thin Client for more information. Remotely or locally configure a thin client using a browser. See Configuring a Thin Client Agent on page 255 for more information. End or maintain a user session after exiting the host operating system. See Understanding User Session States When Logging off Thin Clients on page 262 for more information. Logging in to a Host from a Thin Client To login to a host, double-click the Sentral icon on the thin client desktop. The thin client login screen, shown in the following figure, is displayed. Figure 77. Thin Client login screen 253

266 The following table describes the fields and buttons in this screen. Table 25. Thin client login screen fields Field Host Name Description This field specifies the host or VM that is the connection target. When the Override Host Name parameter is enabled on this thin client, this field is user-editable. When the Override Host Name parameter is not enabled, this field is grayed out. This button refreshes the Host Name field by querying the Sentral Server for the next available host for this thin client or user. User Name User Password User Domain Screen Resolution Color Depth Bitmap Cache Last Connection Required. This field specifies the name of the user to be logged in. Required. This field specifies the user's password. Required. This field specifies the domain to log in to for this session. This pull-down menu lists the available screen resolutions. This pull-down menu lists the available color bit depths. Choices include 8, 16, and 24 bit. The default selection is 24 bit. This field specifies whether to select the bitmap cache. Selecting the bitmap cache can improve performance on some systems. This field specifies whether to display the name of the last host or VM to which the thin client made a connection. Note: Reaching the host's login constitutes a connection. A failed login because of a bad user name, password, or domain still populates this field even though the login failed. This button sets the Host Name field to the last connected host or VM Connect Shutdown Reboot This button starts the connection process when all of the required fields are filled in. If the host name field is empty, then an automatic query to the Sentral Server for the next available host is made on behalf of this thin client or user. This button shuts down the thin client. This button reboots the thin client. Configuring Single Sign on from I9440 I/Port If you are using a firewall with I9440 I/Ports, you must open port 2000 to enable the single sign on feature. For more information about open ports required in your Sentral environment, see Configuring Inbound Network Ports on page 21. For information about opening ports in Windows operating systems, see Configuring Network Ports on Windows XP on page 21 and Configuring Network Ports on Microsoft Vista on page ClearCube Technology, Inc.

267 Chapter 11: Thin Client and Thin Client Agent Configuring a Thin Client Agent You can configure thin clients in multiple ways: ClearCube recommends pushing configuration settings to thin clients by specifying values in the Sentral console configuration screen and then running a discovery. This pushes a configuration file to each thin client on the subnet you discover. For more information about setting configurations and discovering thin clients, see Using the Configuration Screen on page 89, Discovering Sentral Nodes on page 109, and Discovering Thin Clients on page 149. If the Sentral server is offline, you can use the Web based Thin Client Manager interface to configure individual thin client agents in your enterprise. This section describes how to use the Web based Thin Client Manager. Logging in to Thin Client Manager To access the Thin Client Manager, you need to log in to the thin client running the thin client agent that you want to configure. Perform the following steps: 1. Type the following URL in a Web browser: where thinclientname is the host name of the thin client running the thin client agent that you want to configure (consult the Sentral console to determine the thin client host name). The Sentral Thin Client Login screen is displayed, as shown in the following figure. Figure 78. Web Based Thin Client Login Screen 2. Type the following in the appropriate text boxes: Local username for the thin client Password for the thin client user Domain name Sentral Administrator s Guide 255

268 3. Click Login to display the Welcome to Thin Client Manager screen, as shown in the following figure. Figure 79. Welcome to Thin Client Manager Screen You can perform the following tasks from the Thin Client Manager: Configure a thin client Change the local thin client user name and password Get thin client information The following sections describe how to perform each task. Configuring a Thin Client Agent from Thin Client Manager 1. Log in to Thin Client Manager as described in Logging in to Thin Client Manager on page From the Welcome to Thin Client Manager screen, click Configure Thin Client to display the Thin Client Manager Configuration screen, as shown in the following figure. Figure 80. Thin Client Manager Configuration Screen 3. Specify values in each field, as appropriate for your environment. The following table details the Thin Client Manager configuration fields. Table 26. Thin Client Manager Configuration Fields Field Primary Server Description Required. This field specifies the name or IP address of the Primary Sentral server. 256 ClearCube Technology, Inc.

269 Chapter 11: Thin Client and Thin Client Agent Table 26. Thin Client Manager Configuration Fields (continued) Secondary Server Thin Client Health update interval(sec.) Save Field Click here to configure Stand- Alone Server. Description This field specifies the name or IP address of the Secondary Sentral server. If using only one Sentral serve, re-enter the primary's name or use the click here option. Required. This field specifies how often, in seconds, the thin client reports its status and heartbeat to the Sentral server(s). Click Save when all fields have been filled. Click this link you do not have a secondary Sentral server in your environment. 4. Click Save to save your changes. Thin Client Manager displays the following confirmation message: Successfully saved new configuration. You must disable Write Filter to save changes permanently. Click here to disable it. If you click the link in the message, the Thin Client Manager displays the following message: Write Filter has been disabled on the I/Port. Going to restart the system. After a moment, the thin client restarts. If you need to make additional thin client changes, you need to log in to the thin client again. If you are accessing the thin client remotely, you will not be able to log in to the thin client until after the thin client restarts. Changing Local Thin Client User Name and Password 1. Log in to Thin Client Manager as described in Logging in to Thin Client Manager on page From the Welcome to Thin Client Manager screen, click Change Password to display the Change Pass screen, as shown in the following figure. Sentral Administrator s Guide 257

270 3. Specify values for a new user name, a new password, or both. 4. Click Save to save the new account information. Thin Client Manager displays the following confirmation message: Successfully saved new configuration. You must disable Write Filter to save changes permanently. Click here to disable it. If you click the link in the message, the Thin Client Manager displays the following message: Write Filter has been disabled on the I/Port. Going to restart the system. After a moment, the thin client restarts. If you need to make additional thin client changes, you need to log in to the thin client again. If you are accessing the thin client remotely, you will not be able to log in to the thin client until after the thin client restarts. Retrieving Thin Client Information 1. Log in to Thin Client Manager as described in Logging in to Thin Client Manager on page From the Welcome to Thin Client Manager screen, click Get Thin Client Information to display the Thin Client Manager screen. 3. The following table details the each field in the screen. Table 27. Thin Client Manager Fields Field Thin Client Name Thin Client Address Host Name User Name Domain Name Disconnection Reason Description Specifies the thin client s host name. Specifies the IP address of the thin client. Specifies the host or VM to which this thin client was most recently connected. Specifies the user name used in the most recent login. Specifies the domain name used in the most recent login. Specifies the reason for the most recent disconnection. Primary Admin Console Specifies the Primary Sentral server to which this thin client reports. Secondary Admin Console Refresh Time (Sec) Specifies the Secondary Sentral server to which this thin client reports. If same name as the Primary then there is no Secondary Server. Specifies how often, in seconds, the thin client reports its status and heartbeat to the Sentral server(s). 258 ClearCube Technology, Inc.

271 Chapter 11: Thin Client and Thin Client Agent Table 27. Thin Client Manager Fields (continued) Field Description Back Click this link to display the Welcome to Thin Client Agent Manager screen. Using a Web-Based Thin Client This section describes how to connect to a host using a Web browser instead of a thin client. Web-based access, or clientless access, assigns a user to a host based on Sentral user allocations (for more information about user allocations, see Map a Host to a User on page 138, Managing Users on page 171, and Mapping and Allocation Tasks on page 205). The following steps assume you are using Internet Explorer. Perform the following steps to connect to a host using a Web browser. 1. Ensure that TCP connections through port 8080 are enabled if you are connecting through a firewall. For more information, see Enabling Systems for Remote Access on page 20 and Configuring Inbound Network Ports on page Open a Web browser and enter the following URL: where ServerName is the computer name or IP address of the host to which you are connecting. Sentral Administrator s Guide 259

272 The following figure shows the screen displayed upon connection. Click Connect. 3. The first time you click the Connect link from a particular computer, the following dialog box is displayed. Click Install to install an RDP client as an ActiveX control. Downloading and installing the control may take several minutes, depending on your connection to the Sentral server. This installation only occurs the first time you log in through the Web. NOTE If you are using Mozilla Firefox, you are prompted to download a Java applet to provide this functionality. 260 ClearCube Technology, Inc.

273 Chapter 11: Thin Client and Thin Client Agent 4. After RDP control installation, the Blade Web Connection login screen is displayed, as shown in the following figure. You can now specify settings, including the resolution and color depth best suited to the tasks you wish to perform and the connection capabilities of your network. See the following section for more information about configuring the login screen. Configuring the Thin Client Login Screen You can configure the following aspects of the thin client login screen: Default resolution Default color depth Default user Default password Default domain To configure the thin client login screen, edit the ServerConfiguration.xml file located in the following directory of the computer running the Tomcat service: C:\Program Files\Apache Group\Tomcat 4.1\webapps\CMSServer\WEB-INF\ configuration\properties Sentral Administrator s Guide 261

274 The following table lists the lines to change in the file and provides a brief description of each line. Change the values in italics in the Line column to the appropriate value listed in the Values column. Table 28. ServerConfiguration.xml and thin client agent Login Properties Property Line Values Default resolution Default color depth <entry key="web.login.default.resolution">n</entry> <entry key="web.login.default.colordepth">n</entry> x 480 resolution x 600 resolution x 768 resolution 0 8-bit 1 16-bit 2 32-bit Default user <entry key="web.login.default.user">myuser</entry> This value is stored in plain text. Default password Default domain Default domain for I94xx I/Port <entry key="web.login.default.pass">myadmin</entry> <entry key="web.login.default.domain">mydomain</entry> <entry key="iport.login.domain.list >LOCAL</entry> This value is stored in plain text. This value is stored in plain text. This value is for I94xx I/Port login screen only. Values specified here are displayed in the I94xx I/Port login screen domain field. The default value is local. This tag can contain multiple values separated by commas. Understanding User Session States When Logging off Thin Clients This section describes options that RDP thin client users have when exiting a host, and how each option affects the state of their current session. When a user connected to a host running a Windows operating system attempts to exit the operating system, Windows displays the following options: Log Off Disconnect 262 ClearCube Technology, Inc.

275 Chapter 11: Thin Client and Thin Client Agent The following figure shows the Log Off and Disconnect options. Figure 81. Log Off and Disconnect options on a thin client using RDP The following sections describes each option. Log Off When a user click Log Off, as shown in Figure 81, Sentral ends the user s session on the host and makes the host available for other users. Disconnect and the Sentral Follow Me Feature XPe thin client users, especially mobile users who frequently use different XPe thin clients, can take advantage of the Follow Me feature. Sentral Administrator s Guide 263

276 When a user clicks Disconnect (shown in Figure 81) on a thin client running Windows XPe, the session on the host they are connected to persists (that is, Sentral does not end the user session like it does when a user clicks Log Off). When the user logs in again from any thin client in your enterprise, their session on the same blade resumes. 264 ClearCube Technology, Inc.

277 Appendix A: Troubleshooting This section lists some common issues and resolutions encountered so far with ClearCube Sentral Version 5.8. These types of issues are described: Installation Issues Database Issues Authentication Issues Configuration/Operation Issues What to Do First Verify that you are properly authenticated for Apache Tomcat (see Configure Tomcat Authentication for Sentral Server on page 36) and restart the Apache Tomcat service. This resolves most Sentral issues. NOTE Create a desktop shortcut for the Apache Tomcat service. If Firewall issues have been resolved and the ports indicated above have been opened, but you are still faced with connectivity problems and cannot contact devices managed by Sentral, the following tests may help to further isolate the problem. DNS Resolution Checks Verify that Hosts are available by DNS name by using the nslookup tool provided by MS Windows and that the DNS name is resolving to the appropriate IP address for the host. H:\>nslookup Default Server: cct2k3ad2.clearcube.com Address:

278 > iport29.clearcube.com Server: cct2k3ad2.clearcube.com Address: Name: iport29.clearcube.com Address: Ping Checks Verify network connectivity between hosts and console or server machines by using a network ping test. The ping utility is provided by the Microsoft Windows operating system, as well as the Neolinux operating system on the Neolinux Thin Clients. A successful test will result in replies from the remote host as shown below. H:\>ping console.clearcube.com Pinging console.clearcube.com [ ] with 32 bytes of data: Reply from : bytes=32 time<1ms TTL=127 Reply from : bytes=32 time<1ms TTL=127 Reply from : bytes=32 time<1ms TTL=127 Reply from : bytes=32 time<1ms TTL=127 Ping statistics for : Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Problem occurred while loading Authentication Module You may see an authentication module loading problem when trying to load Sentral. If you see this error, restart the Tomcat service. 266 ClearCube Technology, Inc.

279 Appendix A: Troubleshooting Installation Issues An InstallShield error occurs that stops the installation Sentral should be installed while being physically present on the machine. In some cases, installation errors from InstallShield occur when installing over RDP. If you need to install Sentral remotely, you may want to use a Virtual Network Computing (VNC) environment instead. For more information, please see Tomcat does not find the correct version of Java Runtime Environment on the machine The correct version of Java is 1.5.0_08. If the Sentral installer finds an older version of Java, it will prompt you to manually remove it prior to starting the installer. If the Apache Tomcat installer finds another version, first check to see if a different version is installed. The installer should detect this automatically, but there are some cases where it doesn't. Uninstall the other version, and restart the Sentral install process. If a previous version of Java is uninstalled, its folder may not be uninstalled, or its environment variable may be set incorrectly. If this happens, Java 1.5.0_08 will not work. After uninstalling a previous version of Java, check the Program Files\Java\ directory and verify that the previous version s folder has been deleted. If no other version is installed, check to see whether the JAVA_HOME environment variable exists on this machine. If it does, ensure that it points to the Java 1.5.0_08 installation. To find the environment variables, right click My Computer and choose Properties. Click the Advanced tab and click the Environment Variables button at the bottom. If Java is not installed on the system, but the environment variable is there, delete it and restart the Sentral installation. Sentral components are not in Add/Remove Programs You may have installed them under a different profile. Please check by logging into the machine as the same user who installed Sentral to see if they show up. Sentral Administrator s Guide 267

280 Application does not load after login screen If the MS SQL server is paused, you will not receive a database connection error, and the application will not load after the login screen. Make sure that the MS SQL server is not paused. Go to the MS SQL server system. The task bar on this system displays a small database icon for the MS SQL Service Manager. This icon allows pausing, stopping, and starting the service. If the service is stopped or paused, start or restart it. Database Issues Unable to drop the previous CMS database from your MS SQL database server Sometimes other users may be connected to the database. If there is such a connection and you try to drop the database, it will stop you. If you are absolutely sure that you can drop the database, stop and restart the MS SQL service from its task bar icon. (This service can also be accessed from the Services Control Panel under Administrative Tools). This kills all connections, and lets you drop the database. Error 4261: Database connectivity has been lost. Please close Sentral and Restart Tomcat Troubleshooting MySQL 1. Verify that correct version of MySQL is installed and running. a. From the Start menu, run the MySQL command line client. b. Enter the password for root. c. Enter status; to return the version of MySQL installed on the machine. The correct version is Verify that the correct version of the schema was used. See the installation CD for the latest schema scripts and installation instructions. 3. Make sure that your installation of MySQL allows users to connect remotely to the machine. This can be checked and set via the MySQL server instance config wizard. This is installed with MySQL and is available from the Start menu. 268 ClearCube Technology, Inc.

281 Appendix A: Troubleshooting On the screen that requires you to put in the username and password almost at the end, make sure you check the Enable root access from remote machine checkbox. 4. Check that the tables were created properly and respond to SQL queries. a. From the Start menu, run the MySQL command line client. b. Enter the password for root. c. Enter connect CMS; to connect to the CMS database. d. Run the following sample commands: my-sql>connect CMS; my-sql>select * from Alerts; my-sql>select * from functionalview; You should not see any errors come up. If you do see errors, your schema file may be incorrect. e. You may also use a third -party utility such as MySQL Administrator to verify the existence of your database. 5. Make sure the hibernate.cfg.xml file has all the correct tags and information. The file is located at: c:\program files\apache group\tomcat 4.1\webapps\CMSServer\WEB-INF \configuration\properties This file contains information that is populated at the time of the Console installation. The following tags are important for MySQL to work properly: <property name="dialect">org.hibernate.dialect.mysqldialect</property> <property name="connection.driver_class ">com.mysql.jdbc.driver</ property> <property name="connection.url">jdbc:mysql://sentral1/cms</property> <property name="connection.username">root</property> <property name=" connection.password">clearcube</property> Make sure that the when using MySQL, these lines are not commented out. Make sure that the username is correct and that the password is encrypted. You can verify this from the main menu by clicking Setup > Configuration, and then clicking Database Connectivity Test in the Tasks menu. Fill in the values as appropriate and then click Test Connection. If the test is not successful, verify your settings in the Setup - Configuration screen. 6. Make sure that you have the port of MySQL open. By default, this port is Sentral Administrator s Guide 269

282 7. Determine that there are no network problems in reaching the machine with the MySQL installation. 8. Restart the Apache Tomcat server and make sure it has administrative privileges. 9. Reload Sentral Console. Troubleshooting MS SQL 1. Make sure that a network connection between the Server machine and the database server still exists. You can do so by pinging the machine. 2. Make sure that the MS SQL service is running on the database server. 3. You must have SP3a or SP4 installed on the MS SQL server, or any necessary SPs for the SQL server you are running. Use the following script to check the version: SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY('productlevel'),SERVERPROPERTY(edition') This returns the product version, product level, and edition of the MS SQL server installed. 4. Verify that the correct version of the Schema was used. See the installation CD for the latest schema scripts and installation instructions. 5. Make sure the hibernate.cfg.xml file has all the correct tags and information. The file is located at: c:\program files\apache group\tomcat 4.1\webapps\CMSServer\WEB-INF\ configuration\properties This file contains information that is populated at the time of the Console installation. The following tags are important for MS SQL to work properly. <property name="dialect">org.hibernate.dialect.sqlserverdialect</ property> <property name="connection.driver_class"> com.microsoft.sqlserver.jdbc.sqlserverdriver </property> <property name="connection.url"> jdbc:sqlserver:// umair1:1433;databasename=cms; </property> <property name="connection.username">sa</property> <property name="connection.password">clearcube</property> 6. Make sure that the port is open for MS SQL. By default, this port is Restart the MS SQL service. 270 ClearCube Technology, Inc.

283 Appendix A: Troubleshooting 8. Restart the Apache Tomcat Server and make sure it has administrative privileges. 9. Reload Sentral Console. Authentication Issues Sentral fails to authenticate with a valid username and password Use the CCT User account to configure authentication if you are not a local admin user or a domain user. If authentication issues persist, there could be certain security policies that may restrict Sentral to authenticate properly. Run the Test_Authentication.bat script in the Tools\Sentral Authentication Test Tool directory on the Sentral installation CD. To use this utility, perform the following steps: 1. In the.. \configuration\properties folder, go to the configuration.xml and put in your security group. By default it is set to domain users in this script. 2. Run the Test_Authentication.bat script. 3. This opens a login screen. Enter your credentials. 4. The script generates the following files: AuthenticationScript.txt..\ configuration\log\debuginfo.txt..\configuration\log\application.output 5. Return these files to ClearCube for root cause analysis. 6. For NT mode authentication, go into the configuration.xml file and change AD to NT <entry key="active.domain.type">nt</entry> and then repeat the process, starting with step 2. Sentral Administrator s Guide 271

284 Error Code 4282 Problem occurred in loading Authentication module You may see an authentication module loading problem when trying to load Sentral. If you see this error, restart the Tomcat service. If the problem recurs, perform the following steps: 1. Verify that you have the correct version of MySQL (version ), or MS SQL (version SP3). 2. Verify that you have the correct MySQL schema script. See the installation CD for the latest schema scripts and installation instructions. 3. Check the ConsoleConfiguration.xml file for errors. This file is located at: c:\program files\clearcube Sentral\ClearCube Sentral Console\CMS \configuration\properties\ Check that the primary and secondary servers are correct in the configuration. 4. Check the ServerConfiguration.xml for errors. This file is located at: c:\program files\apache group\tomcat 4.1\webapps\CMSServer\WEB-INF\ configuration\properties Check that the primary and secondary servers are correct in the configuration. 5. Verify that you can reach the server installation machine by pinging it by both hostname and IP. 6. Verify that Tomcat is responding. From a browse, enter the following URL: This should load up the Apache Tomcat page. If the page does not load, then the Apache Tomcat Server and needs to be restarted. 7. Make sure that the service is running with proper credentials. 8. Log in to Sentral again. Sentral chassis serial numbers do not match Sentral and the RMM may report different serial numbers for the same chassis. If you experience this problem, make a note of the differing information, and flush the 272 ClearCube Technology, Inc.

285 Appendix A: Troubleshooting database. Rediscovering the network should resolve the problem. If the problem recurs for this chassis, contact Support. Configuration/Operation Issues Renaming a Host does not appear to take effect In some instances, a renamed host may not show its new name in the Hierarchical view. To resolve this issue, restart Apache Tomcat. Sentral does not recognize a replaced Management module When an R4300 Management module such as an 8x8 Connect Module (XCM) is removed and replaced by a User Connect Module (UCM) or an Administrator Connect Module (ACM), Sentral may not record the change, and reports that it still is operating on the XCM. To resolve this issue, reboot the RMM and then refresh the Chassis View in Sentral. Host Agent does not update When you update host agent in the Update Host Agent screen, you schedule a time for the update to occur. When the scheduled time arrives, a DOS window pops up as the.run file is executed. This window does not last long, and the update may fail or succeed. If the window contains a line starting with this message: <html>access DENIED</html> it indicates that the update has failed. To resolve this issue, do another Discovery for the host agent and reschedule the update. A DOS window containing a line starting with this message: <html>success</html> indicates that the update was successful. Sentral Administrator s Guide 273

286 Configuration View of the Primary chassis not working properly If the Configuration View for a Primary chassis appears to work incorrectly, check its IP address configuration. The IP Mode parameter on the RMM (configured through telnet) and its respective parameter in Sentral must match. The settings are Static or DHCP. When the Sentral Server IP address is manually changed, or is updated by DHCP, it also changes the Log Server and Alert Server IP addresses to reflect the same IP that was entered in for the Sentral Server. To troubleshoot this issue, verify the IP Mode settings and the listed IP addresses. Correct these if necessary. When finished, reboot the RMM, restart Apache Tomcat, and restart Sentral. Security groups missing in Configuration, Security, or Advanced Security screens The Configuration, Security, or Advanced Security screens may not display all of your security groups. To troubleshoot this issue, perform the following steps: 1. Check that all security group names are in the securitygroup table in your database. If you are using MS SQL, go to Start Microsoft SQL Server Enterprise Manager. Select Microsoft SQL Servers SQL Server Group Local Databases CMS Tables securitygroup. This table should contain all of your security groups. 2. Verify the maximum security group name s length. In the securitygroup table, the SecurityGroupName parameter is set to size 50. If you have a security group name with more that 50 characters, the securitygroup table is truncated at this particular security group s name. Increase the SecurityGroupName parameter to at least the length of your longest security group name. 3. Restart the Sentral Server machine and attempt to login again. 4. Verify that all security groups are present. If they are still not present, contact ClearCube Technical Support for more testing steps. 274 ClearCube Technology, Inc.

287 Appendix A: Troubleshooting Some nodes appear to be unavailable, even though they are listed in the Sentral database Occasionally, Sentral may appear to lose connectivity, and may generate error messages. The following figure shows a sample message. Figure 82. Host Error Message When this specific message is encountered, try resetting the RMMs in that Control Chain (Chassis Group) to resolve the problem. If this is unsuccessful, verify the firmware versions of the RMMs and the BIOS versions of the hosts or blades in the Control Chain, and update if necessary. All RMMs in your network should have the same firmware version, and all RMMs on a single Control Chain must have the same firmware version. Hosts should always have the latest BIOS version available for that host or blade model unless your site has specific BIOS requirements. The ClearCube Support Web site has updated firmware and BIOS packages available for download. RDP Thin Clients Won t Connect to Hosts Check the Shared Connection Limit. As the default, Sentral is set up to allow only one connection at a time. A modification must be made to the configuration files of the Sentral server to allow for more than one connection to be given out at a time. 1. Edit the following file to increase the session limit in Sentral. This controls how many sessions Sentral will allow a host to have in shared/dedicated mappings. C:\Program Files\ApacheGroup\Tomcat4.1\webapps\CMSServer\WEB-INF\ configuration\properties\serverconfiguration.xml 2. Search for and change this setting: the default is 1. <entry key="shared.connection.limit">4</entry> 3. Change from 1 to 4. "4" allows 4 RDP sessions to a host. 4. Save the changes and close the file. 5. Restart the Apache Tomcat service. Sentral Administrator s Guide 275

288 276 ClearCube Technology, Inc.

289 Appendix B: Events and Alerts The R4300 RMM sends events to Sentral for logging purposes. Two kinds of events are provided, Alerts and Log Entries. All events are logged. The following table lists the events sent by the RMM. RMM Events or Alerts are reported by Sentral as follows: RMM Level 0 Sentral level Low RMM Level 1 Sentral level Medium RMM Level 2 Sentral level High Table 29. RMM Events and Alerts Event States String Level Alert? Cage Temp 1 4 Above max Below min Cage_Temperature+High+<TEMP> Cage_Temperature+Low+<TEMP> Level 0 Alert Cage Fan 1 4 Above max Below min Cage_Fan+Speed+High+<RPM> Cage_Fan+Speed+Low+<RPM> Level 0 Alert Cage Volt 1 3 Above max Below min Cage_Voltage+High+<VOLT> Cage_Voltage+Low+<VOLT> Level 0 Alert Blade Temp Above max Below min Blade_Temperature+High+<TEMP> Blade_Temperature+Low+<TEMP> Level 0 Alert Blade fan Above max Below min Blade_Fan+Speed+High+<RPM> Blade_Fan+lSpeed+Low+<RPM> Level 0 Alert Blade voltage Above max Below min Blade_Voltage+High+<VOLT> Blade_Voltage+Low+<VOLT> Level 0 Alert Cage presence Inserted Removed Cage+Discovered+<CageSN> Cage+Discovered+Primary+<CageSN> Cage+Discovered+Secondary+<CageSN> Cage+Undetected+<CageSN> Level 1 Alert Module 1 4 Inserted Removed Module+Inserted+<ModuleSN> Module+Removed+<ModuleSN> Level 1 Alert Power supply 1 2 Inserted Removed Power_Supply+Inserted Power_Supply+Removed_Bad Level 0 Alert 277

290 Table 29. RMM Events and Alerts (continued) Event States String Level Alert? Backpack Factory defaults Backpack+Defaults+Reset Level 0 Daisy Chain Admin detect Spare detect Admin+Daisy-chain+Detected+Initiated Spare+Daisy-chain+Detected+Initiated Level 2 Blade Inserted Removed Reset MSL enable MSL disable Digital link lost Blade+Inserted+<BladeSN> Blade+Removed+<BladeSN> Blade+Reset+<BladeSN> Blade+MSL+Enable+<BladeSN> Blade+MSL+Disable+<BladeSN> Blade+Digital+Link+Lost+<BladeSN> Level 1 Level 1 Level 1 Level 0 Level 0 Level 1 Cage Setting Switch change Config setting Fan override Cage+Switch+<CageSN>+< SWdata> Cage+Config.+Setting+Changed+<CageSN> Cage+Fan+Override+<CageSN> RMM promoted to secondary++<cagesn> Level 1 Alert Firmware upgrade RMM firmware FPGA firmware PSoC firmware RMM+Firmware+Update+<pass/fail> ACM+ Firmware+Update+<pass/fail> XCM+ Firmware+Update+<pass/fail> UCM+ Firmware+Update+<pass/fail> FPM+ Firmware+Update+<pass/fail> Level 1 Alert Failover Failover occurred failover+<newbp#>+<newrmm#>+ <failed_ipaddress> Level 0 Alert DHCP Changed DHCP+Address+Change+<RMM#>+<RMMip> StaticIp+Address+Change+<RMM#>+<RMMip> Level 2 Event History Event History Purged Event+History+Cache+Purged Level ClearCube Technology, Inc.

291 Appendix C: Uninstalling Sentral Sentral and its components require separate uninstallation procedures. Administrator access is required for all uninstallations. Uninstall all Sentral components from the Add/ Remove Programs Control Panel. perform the following steps: 1. Go to Start > Control Panel > Add/Remove Programs. 2. Select the Sentral application from the list of programs. Click the Change/ Remove button. 3. Select the radio button for Remove. Click Next. 4. Once the removal is complete, click the Finish button. Always uninstall the components in this order: 1. Sentral component application (if installed on the same machine, the Sentral Server, Console, and FTP Server can be uninstalled in any order) 2. Apache Tomcat (if installed) 3. ClearCube Perl Plugin (if installed) 4. ActivePerl (if installed) 5. Java Runtime Environment (JRE) If ActivePerl is uninstalled before the ClearCube Perl Plugin is uninstalled, the uninstallation of the ClearCube Perl Plugin fails. To fix this, reinstall ActivePerl, uninstall the ClearCube Perl Plugin, then uninstall ActivePerl if desired. When uninstalling the Sentral XPe thin client agent, you need to uninstall it using the same method you used to install it. This means that if you used NeoWare ezremote Manager to install the thin client agent as a snap-in, you need to use ezremote Manager to uninstall it. An uninstallation snap-in is provided on the Sentral installation CD. If you installed the thin client agent with the stand-alone installer (setup.exe) or if you have a factory-installed client, use Add/Remove Programs from the Control Panel or the installer setup.exe program to uninstall the client. 279

292 280 ClearCube Technology, Inc.

293 Appendix D: References This section of the manual provides a collection of items that might be of interest to the Sentral User or Administrator. There are several components in this section that may help with design, layout, or implementation of your assets and Sentral management of those assets. ClearCube will maintain the latest level of information in this manual on the ClearCube Support Site. The information here is intended for reference only and is not supported by ClearCube. As always you can receive technical support for Sentral and its components from ClearCube Support either by phone: or by web: The following items are included in this section: Restarting Sentral Components Database Connectivity Notes Authentication CCT User Account Admin and Spare Daisy Chains IP Network Basics SNMP Sentral Server Failover Behavior Restarting Sentral Components After completing the Setup Configuration screen, the Primary and Secondary Sentral servers should be restarted to ensure the changes are saved. These servers should also be restarted whenever these parameters are edited: Database Server Name Database User Name Database User Password Database Type 281

294 Database Connectivity Notes Changes that are made to the host agent or the Sentral Server configuration require restarting the Tomcat service for the modifications to take effect. The service also needs to be restarted for tests that check loss of database connectivity. Authentication Host Authentication Steps to perform configuration are as follows when fully authenticating to a domain, services, servers, Console, and host agent applications. 1. Configure and authenticate ALL hosts to the domain to be used. These hosts would typically include, but are NOT limited to: Hosts where Primary and Secondary servers reside Hosts for all end users/clients (Sentral Console & host agent) reside 2. When installing and selecting servlet component Apache Tomcat to run as a service, the Tomcat service will be required, after installation completes, to be authenticated to the domain. Additionally, this method of running the servlet is useful for trouble shooting purposes. a. Open service by navigating to Start > Settings > Control Panel. b. In the Category View of Windows XP, select Performance and Maintenance > Administrative Tools > Services. c. In the Classic View of Windows XP, select Administrative Tools > Services. d. Using a command prompt, type services.msc. e. Select and stop the Apache Tomcat service. f. Open the properties dialog box by double-clicking the service or using the Action > Properties menu selection while service is selected. g. Select the Log On tab, enter the appropriate information into the Use this account field using the format domain-name\administrator, enter the appropriate passwords, and press OK. h. Message displays stating that selects modified will be applied when the service is restarted. i. Re-start the service. 282 ClearCube Technology, Inc.

295 Appendix D: References j. Verify that the service authenticates to the domain. 3. When installing and selecting Apache Tomcat to run as an application, Tomcat will NOT be required to be authenticated, because an application identifies the host on which it resides, and this host will already be authenticated. Console and Host Agent Application Logon The ability to log into the Sentral Console or Sentral host agent as a local user requires the selection of User Member Groups. Perform the following steps: On the Sentral Console: 1. Log in to the Sentral Console as a user with full local administrative permissions. 2. From the main menu, select Setup Configuration. The Setup Configuration screen is displayed. 3. Scroll down to the Local Security Groups parameter. 4. Select the Local Security Groups applicable for that particular host/user. 5. Press Save. On the host agent: 1. Log in to the Sentral host agent as a user with full local administrative permissions. 2. From the File menu, select Configuration. The Configuration screen is displayed. 3. Select the Local Security Groups applicable for that particular host/user. 4. Press Save. The ability to log into Sentral as a Domain user requires the selection of Domain Security Groups. Perform the following steps: On the Sentral Console: 1. Log in to the Sentral Console as a user with fully authenticated administrative permissions. 2. From the main menu, select Setup Configuration. The Setup Configuration screen is displayed. 3. Scroll down to the Domain Security Groups parameter. Sentral Administrator s Guide 283

296 4. Select the Domain Security Groups applicable for that particular host/user. 5. Press Save. On the host agent: 1. Log in to the Sentral host agent as a user with fully authenticated administrative permissions. 2. From the File menu, select Configuration. The Configuration screen is displayed. 3. Select the Domain Security Groups applicable for that particular host/user. 4. Press Save. Server Authentication Configuring the Primary and Secondary servers to reside independently on different hosts. Primary Server 1. Install the components for the Server and Console applications to reside on an independent host for a Primary server, as described in this guide. 2. Authenticate the primary server host to the domain. Secondary Server 1. Install components for the Server and Console applications to reside on an independent host for a Secondary server, as described in this guide. 2. Authenticate the secondary server host to the domain. Admin and Spare Daisy Chains ClearCube backpacks may be cabled together to provide additional management control for as many as 14 chassis and 112 blades in those chassis. This cabling provides the Administration ability to View directly with out the aid of software real time video, video and Keyboard, and KVM features of each blade in a chassis that is within the Admin Daisy chain. The Spare Daisy Chain provides the capability to provide a user with access and control of a spare blade should his blade have problems. Sparing can take place across as many as 14 chassis. ClearCube has provided the necessary connection ports on the back of the ClearCube chassis to make 284 ClearCube Technology, Inc.

297 Appendix D: References this cabling efficient and provide additional asset management via the Remote Management Module. The Admin Port is a link between an Admin C/Port and the chassis served by that Admin C/Port. An Admin Daisy Chain can connect from 1 to 14 chassis within a single Control Chain. More than one Admin Daisy Chain can be configured on a single Control Chain. The Admin Daisy Chain uses the same ClearCube proprietary data link that connects Hosts to C/Ports. The ability to spare users over is the result of a link between a Spare Blade and the chassis served by that Spare Blade. A Spare Daisy Chain can connect from 1 to 14 chassis within a single Control Chain. More than one Spare Daisy Chain can be configured in a backpack. However, only one Spare switch may be used on a Spare Daisy Chain at any given time. ClearCube recommends 1 to 23 (1 spare in three chassis) or 1 to 31 (1 spare in four chassis) for best utilization of spares. The Spare Daisy Chain uses the same ClearCube proprietary data link that connects Hosts to C/ Ports. Figure 83 on page 286 shows two typical examples of daisy-chaining. The diagram on the left shows a rack of R4300 chassis with a single Admin Daisy Chain and a single Spare Daisy Chain. The diagram on the right shows a rack of R4300 chassis with multiple Daisy Chains. Figure 84 on page 287 shows details of R4300 Daisy chains. Figure 85 on page 288 shows details of R4200 Daisy chains. Figure 86 on page 289 shows details of mixedmode daisy chaining, with a combination of two R4300s and one R4200 Daisychained together. Sentral Administrator s Guide 285

298 Spare Configuration Cable Admin C/Port and Terminal Primary Chassis with E-net Control Link To Network Admin C/Port and Terminal #1 Spare Configuration Cable Primary Chassis with E-net Control Link To Network Spare Daisy Chain Spare Daisy Chain #1 Admin Daisy Chain Admin Daisy Chain #1 Control Chain Control Chain Spare Configuration Cable Admin C/Port and Terminal #2 Spare Daisy Chain #2 Admin Daisy Chain #2 Control Chain with Single Daisy Chains Spare Daisy Chain #3 Spare Configuration Cable Control Chain with Multiple Daisy Chains Figure 83. Daisy-Chain Examples 286 ClearCube Technology, Inc.

299 Appendix D: References Admin C/Port and Terminal Primary Chassis with E-net Control Link Spare Configuration Cable To Network Spare Daisy Chain Secondary Chassis with E-net Control Link Admin Daisy Chain To Network Tertiary Chassis No E-net Control Link Control Chain Figure 84. R4300 Daisy-Chain Cabling Example Sentral Administrator s Guide 287

300 Admin C/Port and Terminal Spare Configuration Cable CLEARCUBE Admin C/Port Primary Chassis with RMC To Network Control Chain Admin Daisy Chain Tertiary Chassis (No RMC) Spare Daisy Chain Tertiary Chassis (No RMC) Figure 85. R4200 Daisy-Chain Cabling Example 288 ClearCube Technology, Inc.

301 Appendix D: References Admin C/Port and Terminal Primary R4300 with E-net Control Link CLEARCUBE Spare Configuration Cable Admin C/Port To Network Spare Daisy Chain Secondary R4300 with E-net Control Link Admin Daisy Chain To Network Control Chain Tertiary BSBP R4200 No RMC No E-net Control Link Figure 86. Mixed-Mode Daisy-Chain Cabling Example Sentral Server Failover Behavior Sentral Failover allows Sentral to keep operating in case the primary Sentral server is unable to operate. When Sentral failover occurs, Sentral Console operations are switched from Sentral's primary server to Sentral's secondary server. The switch to the secondary is automatic and can easily go unnoticed by the console administrator. A way to determine if the Sentral Console is using the secondary Sentral server is to go to the Setup Configuration screen and observer the value of the Server Type. If a failover is in effect, the Server Type indicates Secondary (or Stand-alone). If failover is not in effect, then the Server Type indicates Primary. No special setup is required for failover to function. Of course, a running secondary Sentral server must be specified. The Setup Configuration screens of the primary and secondary servers do not have to exactly match. There may be good reasons for some differences. However, to minimize failover behavior differences between the primary and secondary servers these Setup Configuration fields should match on both the primary and secondary servers. Sentral Administrator s Guide 289

302 Table 30. Console Configuration Parameters That Should Match for Failover Parameter Primary Server Secondary Server Connection Preference Database Server Name Database User Name Database User Password Database Type Discovery User Preference Match? Must match Must match Should match Must match Must match Must match Must match Should match When the Connection Preference and Discovery User Preference parameters do not match, behavior for nodes that connect or attempt to connect will be different after failover. This may be desirable, because it can offer a backup indication that failover has occurred. Primary and Secondary Servers Sharing the Same Database Ideally there would be no discernible difference between primary and secondary operation, however this is not the case. Operations that pull or receive live configuration or health and status data, from managed resources like Hosts, Thin Clients, chassis, etc., continue to function without any noticeable difference when accessed through the secondary. If the primary and secondary servers share the same database (highly recommended), then only defined Alerts and the list of deployed Alerts will differ between the primary and secondary. While in failover any new Alerts defined and deployed from the secondary will not known to the primary when the primary reestablishes its lead role. Alarms generated before, during and after failover are visible to both primary and secondary. While the primary is unavailable, scheduled tasks on the primary, such as scheduled reports and scheduled discoveries will be affected. If scheduled firmware/software updates use services (FTP,TFTP) provided by the primary's host machine, then those updates may be in jeopardy depending on the state of the host. Alerts Sent During Failover Depending on the nature of failover, Alerts sent during failover may not be received. 290 ClearCube Technology, Inc.

303 Appendix E: Contacting Support 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 address to ClearCube Technical Support ClearCube Support Web site (866) Direct line in the US +1 (512) Direct line from outside the US 291

304 292 ClearCube Technology, Inc.

305

306 P/N G Rev I