C
HAPTER
1:
I
NTRODUCTION
3
4.
Paragon II USTs / EUSTs (user station modules or enhanced user station modules)
provide a direct connection to a Paragon II Main Unit for access to the Main Unit itself and
its targets. The connection is made
from
the user station’s “Cat5 Port”
to
the “User Ports” on
the back panel of the Main Unit. This connection is made using a Cat 5e UTP cable with
RJ45 connectors. These two particular user stations function as part of the path for remote
access via the IP-Reach model M2.
5.
An additional
Paragon II UST
or
EUST
allows for local access to the Paragon switch (or
switches) and targets, as described above, and then keyboard, monitor, mouse cables are
connected to PS/2 ports on the rear panel of the UST for use. Authorization and
authentication occur locally since this user station is not controlled by the CommandCenter
Secure Gateway.
6.
IP-Reach (models M1, M2, and TR 364)
provide remote access to targets. Authorization
and authentication occur at CommandCenter Secure Gateway since the IP-Reach is providing
remote access to the Base Unit.
6a.
UST-IP (models USTIP1 and USTIP2)
combine the functionality of an IP-Reach M series
(6) and one or two USTs (4), providing remote and local access to Paragon systems in a
single device. In a Paragon II CommandCenter integration setup, a USTIP unit can be used in
place of separate IP-Reach and UST devices.
7.
Paragon II System Controller
has software that enables it to configure and administer
targets and devices in the Paragon II system. The Paragon II System Controller can
administer up to eight base Paragon switches. The IP-Reach, USTs, and Paragon switches in
the illustration could theoretically be duplicated seven times, and still be administered by a
single Paragon II System Controller, offering a maximum of 1024 targets. Please see
Appendix B: Sample Configurations
for additional information. In order for the Paragon II
System Controller to configure and/or administer all Base M units, and IP-Reach units, all
components must be on the same subnet.
8.
CommandCenter Secure Gateway
provides centralized management, administration,
authentication and authorization for the Paragon II system.
If you are deploying any of these components for the first time, you will find installation and
initial configuration instructions in the appropriate chapters below.
Supported Browsers and Java Runtime Environment
To access CommandCenter Secure Gateway and the network appliances within its control, your
PC must have the correct Java Runtime Environment and must use one of supported browsers.
For a complete list of supported browsers, see the Compatibility Matrix on the Raritan website
(
Important: Depending on the version of your CommandCenter Secure Gateway,
the required Java Runtime Environment version and supported browsers may
be slightly different. Refer to the Compatibility Matrix specific to your version
for details.
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. Browser settings can remain at their defaults, but you should
disable Popup Blocking temporarily to allow the initial CommandCenter Secure Gateway login
screen to be displayed.
Содержание Paragon II
Страница 4: ......
Страница 8: ......
Страница 12: ...4 PARAGON II COMMANDCENTER INTEGRATION SOLUTIONS DEPLOYMENT GUIDE...
Страница 22: ......
Страница 32: ......
Страница 36: ...28 PARAGON II COMMANDCENTER INTEGRATION SOLUTIONS DEPLOYMENT GUIDE...
Страница 40: ......
Страница 50: ...42 PARAGON II COMMANDCENTER INTEGRATION SOLUTIONS DEPLOYMENT GUIDE...
Страница 53: ...APPENDIX A P2SC COMPATIBILITY LIST 45...
Страница 60: ......
Страница 63: ......