This document contains proprietary information that is protected by copyright. All rights reserved. No
part of this document may be photocopied, reproduced, or translated into another language without
express prior written consent of Raritan, Inc.
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a commercial installation. This equipment generates, uses, and can
radiate radio frequency energy and if not installed and used in accordance with the instructions, may
cause harmful interference to radio communications. Operation of this equipment in a residential
environment may cause harmful interference.
VCCI Information (Japan)
Raritan is not responsible for damage to this product resulting from accident, disaster, misuse, abuse,
non-Raritan modification of the product, or other events outside of Raritan's rea son able control or not
arising under normal operating conditions.
The following sections have changed or information has been added to
the CommandCenter Secure Gateway Administrators Guide based on
enhancements and changes to the equipment and/or documentation.
• Discover and Add Devices (on page 15)
• Add User Gr
• Add a KVM
• Devic
• Add an Inter
• Interface
• DRAC 5 Con
• M
• Java RDP Connec
• Interface
• Interface
• Interface
• Node
• Add a User
• Edit a User
• Limit the Nu
• Use
• IBM
• Older Versio
• Con
• What is IP F
• What is IP Is
• Requir
• Acc
• Switch th
• Edit Network
• Power Control of Power IQ IT Devices (on pa
• Con
es CSV File Requirements (on page 55)
icrosoft RDP Connection Details (on page 102)
Control Connections (on page 103)
page 105)
s CSV File Requirements (on page 113)
rs CSV File Requirements (on page 140)
LDAP Configuration Settings (on page 176)
208)
figuring the CC-SG Network (on page 211)
ess a CC-SG Cluster (on page 226)
page 275)
figuring Power IQ Services (on page 305)
oups and Users (on page 19)
or Serial Device (on page 34)
face (on page 99)
s for In-Band Connections (on page 101)
nection Details (on page 101)
tion Details (on page 102)
s for DRAC Power Control Connections (on page 103)
s for ILO Processor, Integrity ILO2 , and RSA Power
s for Power IQ Proxy Power Control Connections (on
Group (on page 132)
Group (on page 133)
mber of KVM Sessions per User (on page 135)
n of Application Opens After Upgrading (on page
ailover mode? (on page 212)
olation mode? (on page 215)
ements for CC-SG Clusters (on page 226)
e Primary and Secondary Node Status (on page 228)
Interfaces Configuration (Network Interfaces) (on
ge 305)
xvi
What's New in the CC-SG Administrators Guide
• Configuring Power Control of Power IQ IT Devices (on page 306)
• CC-SG Clustering (on page 315)
See the Rel
ease Notes for a more detailed explanation of the changes
applied to this version of the CommandCenter Secure Gateway.
xvii
Chapter 1
Prerequisites
Introduction
The CommandCenter Secure Gateway (CC-SG) Administrators Guide
offers instructions for administering and maintaining your CC-SG.
This guide is intended for administrators who typically have all available
privileges.
Users who are not administrators should see Raritan's CommandCenter
Before configuring a CC-SG according to the procedures in this
document, see Raritan's CommandCenter Secure Gateway Deployment Guide for more comprehensive instructions on deploying
Raritan devices that are managed by CC-SG.
Terms and acronyms found in this document include:
Access Client - HTML-based client intended for use by normal access
users who need to access a node managed by CC-SG. The Access
Client does not allow the use of administration functions.
Admin Client - Java-based client for CC-SG useable by both normal
access users and administrators. It is the only client that permits
administration.
Associations - relationships between categories, elements of a category,
and ports or devices or both. For example, if you want to associate the
“Location” category with a device, create associations before adding
devices and ports in CC-SG.
Category - a variable that contains a set of values or elements. An
example of a Category is Location, which may have elements such as
“New York City,” “Philadelphia,” or “Data Center 1.” When you add
devices and ports to CC-SG, you will associate this information with
them. It is easier if you set up associations correctly first, before adding
devices and ports to them. Another example of a Category is “OS Type,”
which may have elements such as “Windows” or “Unix” or “Linux.”
CIM (Computer Interface Module) - hardware used to connect a target
server and a Raritan device. Each target requires a CIM, except for the
Dominion KX101, which is attached directly to one target and therefore
does not require a CIM. Target servers should be powered on and
connected to CIMs, and CIMs should be connected to the Raritan device
BEFORE adding the device and configuring ports in CC-SG. Otherwise,
a blank CIM name will overwrite the CC-SG port name. Servers must be
rebooted after connecting to a CIM.
Device Group - defined group of devices that are accessible to a user.
Device groups are used when creating a policy to control access to the
devices in the group.
Devices - Raritan products such as Dominion KX, Dominion KX II,
Dominion SX, Dominion KSX, IP-Reach, Paragon II System Controller,
and Paragon II UMT832 with USTIP that are managed by CC-SG. These
devices control the target servers and systems, or "nodes" that are
connected to them. Check the CC-SG Compatibility Matrix on the Raritan
Support web site for a list of supported devices.
Elements - values of a category. For example, the “New York City”
element belongs to the “Location” category, and the “Windows” element
belongs to the “OS Type” category.
2
Chapter 1: Introduction
Ghosted Ports - when managing Paragon devices, a ghosted port can
occur when a CIM or target server is removed from the system or
powered off (manually or accidentally). See Raritan's Paragon II User Guide.
Hostname - can be used if DNS server support is enabled. See About
Network Setup (on page 211).
The ho
stname and its Fully-Qualified Domain Name (FQDN = Hostname
+ Suffix) cannot exceed 257 characters. It can consist of any number of
components, as long as they are separated by “.”.
Each component has a maximum size of 63 characters and the first
character must be alphabetic. The remaining characters can be
alphabetic, numeric, or “-” (hyphen or minus).
The last character of a component may not be “-”.
While the system preserves the case of the characters entered into the
system, the FQDN is case-insensitive when used.
iLO/RILOE and iLO2/RILOE2 - Hewlett Packard's Integrated Lights
Out/Remote Insight Lights Out servers that can be managed by CC-SG.
Targets of an iLO/RILOE device are powered on/off and recycled
directly. iLO/RILOE devices cannot be discovered by CC-SG; they have
to be manually added as nodes. In this guide, the term iLO/RILOE
includes both iLO/RILOE and iLO2/RILOE2.
In-band Access - going through the TCP/IP network to correct or
troubleshoot a target in your network. KVM and Serial devices can be
accessed via these in-band applications: RemoteDesktop Viewer, SSH
Client, RSA Client, VNC Viewer.
IPMI Servers (Intelligent Platform Management Interface) - servers that
can be controlled by CC-SG. IPMI are discovered automatically but can
be added manually as well.
Out-of-Band Access - using applications such as Raritan Remote
Console (RRC), Raritan Console (RC), Multi-Platform Client (MPC),
Virtual KVM Client (VKC) or Active KVM Client (AKC) to correct or
troubleshoot a KVM or serial managed node in your network.
Policies - define a user group's access within the CC-SG network.
Policies are applied to a user group and have several control param eters
to determine the level of control, such as date and time of access.
Nodes - target systems, such as servers, desktop PCs, and other
networked equipment, that CC-SG users can access.
Interfaces - the different ways a Node can be accessed, whether through
an out-of-band solution such as a Dominion KX2 connection, or through
an in-band solution, such as a VNC server.
3
Chapter 1: Introduction
Node Groups - a defined group of nodes that are accessible to a user.
Node groups are used when creating a policy to control access to the
nodes in the group.
Ports - connection points between a Raritan device and a node. Ports
exist only on Raritan devices, and they identify a pathway from that
device to a node.
SASL (Simple Authentication and Security Layer) - method for adding
authentication support to connection-based protocols.
SSH - clients, such as PuTTY or OpenSSH, that provide a command line
interface to CC-SG. Only a subset of CC-SG commands is provided via
SSH to administer devices and CC-SG itself.
User Groups - sets of users that share the same level of access and
privileges.
Client Browser Requirements
For a complete list of supported browsers, see the Compatibility Matrix
on the Raritan Support web site.
4
Chapter 2
Accessing CC-SG
You can access CC-SG in several way s:
•Browser: CC-SG supports numerous web browsers (for a complete
list of supported browsers, see the Compatibility Matrix on the
Raritan Support website).
•Thick Client: You can install a Java Web Start thick client on your
client computer. The thick client functions exactly like the browserbased client.
•SSH: Remote devices connected via the serial port can be accessed
using SSH.
•Diagnostic Console: Provides emergency repair and diagnostics only
and is not a replacement for the browser-based GUI to configure and
operate CC-SG. See Diagnostic Console (on page 264).
Note: Use
client, and SSH while accessing CC-SG.
rs can be connected simultaneously, using the browser, thick
In This Chapter
Browser-Based Access via the CC-SG Admin Client ...............................5
The CC-SG Admin client is a Java-based client that provides a GUI for
both administrative and access tasks, depending on your permissions.
1. Using a supported Internet browser, type the URL of the CC-SG and
then type /admin: http(s)://IP address/admin, for example,
http://10.0.3.30/admin (https://10.0.3.30/admin) or
https://10.0.3.30/admi
If you see the JRE Incompatibility Warning window, select the JRE
version that is appropriate for your client computer and install it.
Once JRE is installed, try this procedure again. See JRE
Incompatibility (on page 6).
u can continue without installing a new JRE version.
Or, yo
n.
2. If you see a Restricted Service Agreement, read the agreement text
3. Type your Username and Password and click Log In.
4. Upon valid login, the CC-SG Admin Client opens.
and select the I Understand and Accept the Restricted Service
Agreement checkbox.
5
Chapter 2: Accessing CC-SG
JRE Incompatibility
If you do not have the minimum required version of JRE installed on your
client computer, you will see a warning message before you can access
the CC-SG Admin Client. The JRE Incompatibility Warning window
opens when CC-SG cannot find the required JRE file on your client
computer.
If you see the JRE Incompatibility Warning window, select the JRE
version that is appropriate for your client computer and install it, or you
can continue without installing a new JRE version.
You must launch CC-SG again once JRE is installed.
Administrators can configure the JRE minimum version that is
recommended and the message that appears in the JRE Incompatibility
Warning window. See Configuring Custom JRE Settings (on page
223).
Thick Client Access
The CC-SG thick client allows you to connect to CC-SG by launching a
Java Web Start application instead of running an applet through a web
browser. The advantage of using the thick client instead of a browser is
that the client can outperform the browser in terms of speed and
efficiency. The minimum Java version required for running the thick client
is 1.5.0.10.
Install the Thick Client
To download the thick client from CC-SG:
1. Launch a web browser and type this URL:
http(s)://<IP_address>/install where <IP_address> is
the IP address of the CC-SG.
If a security warning message appears, click Start to continue the
download.
2. When the download is complete, a new window in which you can
specify the CC-SG IP address opens.
3. Type the IP address of the CC-SG unit you want to access in the IP
to Connect field. Once you have connected, this address will be
available from the IP to Connect drop-down list. The IP addresses
are stored in a properties file that is saved to your desktop.
4. If the CC-SG is configured for secure browser co nnections, you must
select the Secure Socket Layer (SSL) checkbox. If the CC-SG is not
configured for secure browser connections, you must deselect the
Secure Socket Layer (SSL) checkbox. This setting must be correct
or the thick client will not be able to connect to CC-SG.
6
Chapter 2: Accessing CC-SG
5. To check the setting in CC-SG: Choose Administration > Security. In
the Encryption tab, look at the Browser Connection Protocol option. If
the HTTPS/SSL option is selected, then you must select the Secure
Socket Layer SSL checkbox in the thick client's IP address
specification window. If the HTTP option is selected, deselect the
Secure Socket Layer SSL checkbox in the thick client's IP address
specification window.
6. Click Start.
A warning message appears if you are using an unsupported
Java Runtime Environment version on your machine. Follow the
prompts to either download a supported Java version, or
continue with the currently installed version.
7. The login screen appears.
8. If the Restricted Service Agreement is enabled, read the agreement
text, and then select the I Understand and Accept the Restricted
Service Agreement checkbox.
9. Type your Username and Password in the corresponding fields, and
then click Login to continue.
Use the Thick Client
The minimum Java version required for running the thick client is
1.5.0.10. Java version 1.6.0 is also supported.
Once the thick client is installed, there are two ways to access it on your
client computer.
To access the thick client:
•Launch the thick client from the Java Control Panel's Java
Application Cache Viewer.
•Use the Java Control Panel's Java Application Cache Viewer to
install a shortcut icon on your desktop for the thick client.
7
Chapter 2: Accessing CC-SG
CC-SG Admin Client
Upon valid login, the CC-SG Admin Client appears.
8
Chapter 2: Accessing CC-SG
•Nodes tab: Click the Nodes tab to display all known target nodes in a
tree view. Click a node to view the Node Profile. Interfaces are
grouped under their parent nodes. Click the + and - signs to expand
or collapse the tree. Right-click an interface and select Connect to
connect to that interface. You can sort the nodes by Node Name
(alphabetically) or Node Status (Available, Busy, Unavailable). Rightclick the tree view, select Node Sorting Options, and then select By
Node Name or By Node Status.
•Users tab: Click the Users tab to display all registered Users and
Groups in a tree view. Click the + and - signs to expand or collapse
the tree.
•Devices tab: Click the Devices tab to display all known Raritan
devices in a tree view. Different device types have different icons.
Ports are grouped under their parent devices. Click the + and - signs
to expand or collapse the tree. Click a port to view the Port Profile.
Right-click a port and select Connect to connect to that port. You can
sort the ports by Port Name (alphabetical), Port Status (Available,
Busy, Unavailable) or Port Number (numerical). Right-click the tree
view, select Port Sorting Options, and then select By Node Name or
By Node Status.
•Quick Commands toolbar: This toolbar offers shortcut buttons for
executing common commands.
•Operation and Configuration menu bar: These menus contain
commands to operate and configure CC-SG. You can access some
of these commands by right-clicking on the icons in the Nodes,
Users, and Devices Selection tabs. The menus and menu items you
see are based on your user access privileges.
•Server time: The current time and time zone as configured on CC-
SG in Configuration Manager. This time is used when scheduling
tasks in Task Manager. See Task Manager (on page 246). This time
may be different than the time your cli
ent PC uses.
9
Chapter 3
Getting Started
Upon the first login to CC-SG, you should confirm the IP address, set the
CC-SG server time, and check the firmware and application versions
installed. You may need to upgrade the firmware and applications.
Once you have completed your initial configurations, proceed to Guided
Setup. See Configuring CC-SG with Guided Setup (on page 13).
In This Chapter
Confirming IP Address.............................................................................10
Setting CC-SG Server Time
Checking the Compatibility Matrix
Checking and Upgrading Application Vers
3. Check that the network settings are correct, and make changes if
needed. See About Network Setup (on page 211). Optional.
4. Click
5. Click Restart Now to confirm your settings and restart CC-SG.
Setting CC-SG Server Time
CC-SG's time and date must be accurately maintained to provide
credibility for its device-management capabilities.
Important: The Time/Date configuration is used when scheduling
tasks in Task Manager. See
set on your client PC may be different than the time set on CC-SG.
Only the CC Super-User and users with similar privileges can configure
Time and Date.
Changing the time zone is disabled in a cluster configuration.
To configure the CC-SG server time and date:
1. Choose Administration > Configuration.
2. Click the Time/Date tab.
a. To set the date and time manually:
Update Configuration to submit your changes.
Task Manager
(on page 246). The time
10
Chapter 3: Getting Started
Date - click the drop-down arrow to select the Month, use the up
and down arrows to select the Year, and then click the Day in
the calendar area.
Time - use the up and down arrows to set the Hour, Minutes, and
Seconds, and then click the Time zone drop-down arrow to
select the time zone in which you are operating CC-SG.
a. To set the date and time via NTP: Select the Enable Network
Time Protocol checkbox at the bottom of the window, and then
type the IP addresses for the Primary NTP server and the
Secondary NTP server in the corresponding fields.
Note: Network Time Protocol (NTP) is the protocol used to
synchronize the attached computer's date and time data with a
referenced NTP server. When CC-SG is configured with NTP, it can
synchronize its clock time with the publicly available NTP reference
server to maintain correct and consistent time.
3. Click Update Configuration to apply the time and date changes to
CC-SG.
4. Click Refresh to reload the new server time in the Current Time field.
Choose System Maintenance > Restart to restart CC-SG.
Checking the Compatibility Matrix
The Compatibility Matrix lists the firmware versions of Raritan devices
and software versions of applications that are compatible with the current
version of CC-SG. CC-SG checks against this data when you add a
device, upgrade device firmware, or select an application for use. If the
firmware or software version is incompatible, CC-SG displays a message
to warn you before you continue. Each version of CC-SG will support
only the current and previous firmware versions for Raritan devices at
the time of release. You can view the compatibility matrix on the Raritan
Support web site.
To check the Compatibility Matrix:
•Choose Administration > Compatibility Matrix.
Checking and Upgrading Application Versions
Check and upgrade the CC-SG applications, including Raritan Console
(RC) and Raritan Remote Client (RRC).
To check an application version:
1. Choose Administration > Applications.
11
Chapter 3: Getting Started
2. Select an Application name from the list. Note the number in the
Version field. Some applications do not automatically show a version
number.
To upgrade an application:
If the application version is not current, you must upgrade the
application. You can download the application upgrade file from the
Raritan website. For a complete list of supported application versions,
see the Compatibility Matrix on the Raritan Support website.
The best practice is to enter Maintenance Mode before upgrading
applications. See Entering Maintenance Mode (on page 193).
Save the application file to your client PC.
1.
2. Click the Application name drop-down arrow and select the
application that must be upgraded from the list. If you do not see the
application, you must add it first. See Add an Application (on page
208).
Click Browse, locate and select the application upgrade file from the
3.
dialog that appears then click Open.
4. The application name appears in the New Application File field in the
Application Manager screen.
5. Click Upload. A progress window indicates that the new application
is being uploaded. When complete, a new window will indicate that
the application has been added to the CC-SG database and is
available to use.
6. If the Version field does not automatically update, type the new
version number in the Version field. The Version field will
automatically update for some applications.
7. Click Update.
Note: Users who were logged in during the upgrade must log out of CCSG then log in again to ensure that the new version of the application is
launched. Also, see Older Version of Application Opens After
Upgrading (on page 208).
12
Loading...
+ 354 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.