Owner's manual

ManualsBrandsRaritan Computer ManualsHardwareCC-SG

161

162

163

164

165

166

167

168

169

170

Table Of Contents

Chapter 1: Introduction
- Prerequisites
- Intended Audience
- Terminology/Acronyms
Chapter 2: Accessing CC-SG
- Browser-Based Access
- Thick Client Access
  - Install the Thick Client
  - Use the Thick Client
- CC-SG Window Components
- Check IP Address, Firmware Version, and Application Versions
- Power Down CC-SG
- Compatibility Matrix
Chapter 3: Configuring CC-SG with Guided Setup
- Prepare to Configure CC-SG with Guided Setup
- Guided Setup Overview
- Start Guided Setup:
- Associations
  - Create Categories and Elements
- Device Setup
  - Discover and Add Devices
- Create Groups
  - Add Device Groups and Node Groups
- User Management
  - Add User Groups and Users
Chapter 4: Creating Associations
- Associations
- Association Manager
Chapter 5: Adding Devices and Device Groups
- The Device Tab
- Device and Port Icons
- Search for Devices
- Add a Device
  - Adding a KVM or Serial Device
  - Adding a PowerStrip Device
- Discover Devices
- Edit Device
  - Edit PowerStrip Device
- Delete Device
- Configure Ports
- Device Management
- Viewing Devices
  - Tree View
  - Custom View
- Special Access to Paragon II System Devices
  - Paragon II System Controller (P2-SC)
  - IP-Reach and UST-IP Administration
- Device Group Manager
Chapter 6: Configuring Nodes and Interfaces
- View Nodes
- Nodes and Interfaces Overview
  - About Nodes
  - About Interfaces
- Add Node
- Add an Interface
- Connect to a Node
- Edit an Interface
- Delete an Interface
- Ping a Node
- Edit a Node
- Delete a Node
- Chat
- Node Groups
Chapter 7: Adding and Managing Users and User Groups
- The Users Tree
- Special User Groups
- Add User Groups
- Edit A User Group
- Delete User Group
- Add User
- Edit a User
- Delete User
- Assign Users To Group
- Delete Users From Group
- Other User and User Group Functions
Chapter 8: Policies
- Controlling Access Using Policies
  - Policy Summary
- Node Groups
- Device Groups
- Policy Manager
- Applying Policies To User Groups
Chapter 9: Configuring Remote Authentication
- Authentication and Authorization (AA)
  - Flow for Authentication
  - User Accounts
- Distinguished Names for LDAP and AD
  - Username
  - Base DN
- AD Configurations
- Add LDAP (Netscape) Module to CC-SG
- Add a TACACS+ Module
  - TACACS+ General Settings
- Add a RADIUS Module
  - RADIUS General Settings
- Specify Modules for Authentication and Authorization
- Establish Order of External AA Servers
Chapter 10: Generating Reports
- Audit Trail Report
- Error Log Report
- Access Report
- Availability Report
- Active Users Report
- Locked Out Users Report
- User Data Report
- Users in Groups Report
- Group Data Report
- AD User Group Report
- Asset Management Report
- Node Asset Report
- Active Nodes Report
- Node Creation Report
- Query Port Report
- Active Ports Report
- Scheduled Reports
- CC-NOC Synchronization Report
Chapter 11: System Maintenance
- Maintenance Mode
- Backup CC-SG
- Restore CC-SG
  - Saving and Deleting Backup Files
- Reset CC-SG
- Restart CC-SG
- Upgrade CC-SG
- Shut Down CC-SG
- Restarting CC-SG after Shutdown
- End CC-SG Session
  - Log Out
  - Exit CC-SG
Chapter 12: Advanced Administration
- Guided Setup
- Message of the Day Setup
- Application Manager
  - Adding, Editing and Deleting Applications
  - Default Applications
- Firmware Manager
- Cluster Configuration
- Configure Security
- Notification Manager
- Task Manager
- CommandCenter NOC
- SSH Access to CC-SG
- Diagnostic Console
Appendix A: Specifications (G1, V1, and E1)
- G1 Platform
- V1 Platform
- E1 Platform
Appendix B: CC-SG and Network Configuration
- Introduction
- Executive Summary
- CC-SG Access via NAT-enabled Firewall
- Security and Open Port Scans
Appendix C: User Group Privileges
Appendix D: SNMP Traps
Appendix E: Troubleshooting
- Client Browser Requirements
Appendix F: Two-Factor Authentication
- Supported Environments
- Setup Requirements
- Known Issues
Appendix G: FAQs
Appendix H: Keyboard Shortcuts

CHAPTER 12: ADVANCED ADMINISTRATION 151

the Fully-Qualified Domain Name (FQDN) if a domain server and domain suffix has been

configured.

4. Click either Primary/Backup Mode or Active/Active Mode. A CC-SG provides two

Network Interface Controllers (NIC). The NICs on a G1 or V1 unit are labeled left-to-right,

on the rear of the unit as follows:

MODEL LEFT-MOST NIC (PRIMARY INTERFACE) RIGHT-MOST NIC

G1 LAN1 LAN0

V1 LAN1 LAN2

The NICs on an E1 unit are different, as follows:

MODEL TOP NIC (PRIMARY INTERFACE) BOTTOM NIC

E1 LAN1 LAN2

One interface could be used by itself or both could be used simultaneously. For simplicity,

the discussion below uses LAN1 as left NIC and LAN2 as right NIC. Some internal

diagnostics and messages may refer to these interfaces as “eth0” and “eth1.”

Note: If both interfaces are disconnected, CC-SG restarts.

A. Choose Primary/Backup mode to implement network failover and redundancy. In this mode,

only one NIC is active at a given point of time and only one network IP address assignment is

possible.

Figure 152 Primary/Backup Network

Typically, both NICs are attached to the same LAN sub-network, but different switches (or

hubs) may be used for reliability. When both NICs are used, a level of network redundancy is

provided. For example, if LAN1 is connected and is receiving a Link Integrity signal, CC-SG

uses this NIC for all communications. In the event of a LAN1 failure, if LAN2 is connected,

CC-SG migrates the assigned (possibly by DHCP) IP address to LAN2. LAN2 will be used

until LAN1 is repaired and returned to service. When this happens, CC-SG reverts to using

LAN1.

As long as one interface is viable, a PC client should not notice any disruption in service

during a failure. CC-SG remains at the same logical IP address, but attempts to keep

communication channels and existing sessions up in the event of possible network failures.

All communication (for example, PC client, Raritan device management, cluster peer, etc.) is

carried over this single communication channel that is maintained by both NICs.