Raritan Engineering Command Center CC-SG ユーザーズマニュアル

ページ / 270
C
HAPTER 
2:
 
A
CCESSING 
CC-SG 
11 
 
 
 
2.  Select an application from the pull-down menu and note the number in the version field. If 
the firmware needs upgrading, see the previous section Check and Upgrade CC-SG 
Firmware Version
 and continue to
 step 3. 
3.  Select the application name that needs to be upgraded.  
4.  Click Browse. 
 
Figure 10 CC-SG Application Search Window 
5.  Click on the Look In drop-down menu and navigate to locate the application on your PC 
where the new firmware resides. When you find the application, select it, and click Open
The application name will appear in the Location field in the Application Manager screen. 
6.  Click  Upload to upload the application. 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 for configuration and 
attachment to a specific port. 
7.  Edit the version field to reflect the new version uploaded, and then click Update
8.  Click Close to close the Application Manager screen. 
 
Connection to Console and KVM Management Appliances 
•  CC-SG may interface with the Console and KVM management appliances of the Dominion 
series and the IP-Reach series. Both serial and KVM devices are supported. 
•  Raritan provides a standard console access, a vt100 Java terminal emulation for remote target 
devices that require a serial connection. In addition, Raritan offers a variety of specialized 
applications that allow users to set up a customized look and feel.  
•  The application interface varies, depending on device type selected. In the case of the KVM 
device, Raritan provides the complete keyboard, video, and mouse (KVM) of the remote 
target system through CC-SG.  
•  CC-SG can also interface with HP servers that have iLO or RILOE access capabilities. In this 
case, CC-SG will launch HP’s own Java management applet when connecting to these 
devices and log into iLO/RILOE without prompting the user to re-authenticate.