C
HAPTER
1:
I
NTRODUCTION
1
Chapter 1: Introduction
Congratulations on your purchase of CommandCenter Secure Gateway (CC-SG), Raritan’s
convenient and secure method for managing various UNIX servers, firewalls, routers, load
balancers, Power Management devices, and Windows servers.
CC-SG provides central management and administration, using a set of serial and KVM
appliances. It is designed to operate in a variety of environments, from high-density Data Centers
to Service Provider environments to corporate environments handling large remote offices.
CC-SG, when used in conjunction with Raritan’s Dominion or IP-Reach port-level management
appliances, streamlines and simplifies the management of the target devices (referred to as
“nodes”), easing administration of data center equipment by connecting to the IP network and
presenting the serial console and KVM ports of all the nodes within the managed network.
Prerequisites
Before configuring a CC-SG according to the procedures in this document, refer to Raritan’s
Digital Solution Deployment Guide
for more comprehensive instructions on deploying Raritan
devices that are managed by CC-SG.
Intended Audience
This document is intended for administrators who typically have all available privileges. Please
refer to
Appendix C: User Group Privileges
. Users who are not administrators usually have
fewer privileges, such as being granted only the Nodes Access privileges. Those users should
refer to Raritan’s
CommandCenter Secure Gateway User Guide
for additional information.
Terminology/Acronyms
Terms and acronyms found in this document include:
•
Access Client
– An 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.
•
Associations
—are the relationship 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 first before adding devices and ports in CC-SG.
•
Category
—is a variable that contains a set 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)—is the 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 need to be rebooted after connecting to a CIM.
•
CommandCenter NOC (CC
NOC
)—is a network monitoring appliance that audits and
monitors the status of servers, equipment, and Raritan devices that CC-SG manages.
•
Device Group
—a 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
—are Raritan products such as Dominion KX116, Dominion SX48, Dominion
KSX440, IP-Reach, Paragon II System Controller, Paragon II UMT832 with USTIP, etc. that
Summary of Contents for CC-SG
Page 2: ...This page intentionally left blank...
Page 26: ...12 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE This page intentionally left blank...
Page 46: ...32 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE This page intentionally left blank...
Page 158: ...144 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE This page intentionally left blank...
Page 228: ...214 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE This page intentionally left blank...
Page 236: ......
Page 246: ...232 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE...
Page 248: ...234 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE...
Page 250: ...236 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE...
Page 256: ...242 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE...