Product Documentation

Before You Begin

Oct 21, 2015

Before you install your Command Center server, make sure that you have the minimum system requirements, such as hardware requirements, operating system requirements, and database requirements. You also need to ensure that the database settings are specified according to Command Center requirements.

This topic includes the following details:

Hardware Requirements

Updated: 2014-10-17

The following table summarizes the minimum hardware requirements for the Command Center servers.

Component

Requirement

Processor type

Pentium 4

Processor speed

1.2 gigahertz (GHz)

Memory

1 gigabyte (GB) RAM

Hard disk space

20 GB

Disk Space for Performance Management

The performance management module plots graphs across three tables. By Default, the first table maintains data for 14 days, with a polling interval of 5 minutes. The second table maintains data from one poll per hour, for 30 days. The third table maintains data from one poll per 24 hours, for 365 days. At the beginning of the 15th day, the data in the first table is overwritten with new data. The data in the other two tables is overwritten on the 31st day and the 366th day, respectively. The following table lists the disk space requirements for using the performance management module in a few sample configurations.

No. of Counters

Polling Interval

No. of Devices

Disk Space Required

Unit

100

5 minutes

10

488

MB

300

5 minutes

10

1.4

GB

500

5 minutes

10

2.4

GB

1000

5 minutes

25

11.9

GB

5000

5 minutes

50

119.1

GB

10000

2.5 minutes

50

426

GB

Operating System Requirements

Updated: 2015-05-13

The following table lists the operating system requirements for installing Command Center.

Operating System

Version

Windows

  • Microsoft® Windows®  2012
  • Microsoft® Windows®  2012 R2 64 bit
  • Microsoft® Windows® 2008
  • Microsoft® Windows® 2008 R2 64 bit

Linux

  • CentOS 6.2 32 bit
  • CentOS 6.2 64 bit
  • CentOS 6.5 32 bit
  • CentOS 6.5 64 bit
  • Red Hat Enterprise Linux 6.2 64 bit
  • Red Hat Enterprise Linux 6.4 32 bit
  • Red Hat Enterprise Linux 6.4 64 bit

Database Requirements

Updated: 2015-04-03

Command Center supports the following databases and their versions.

Database Type

Version

MySQL

5.1.x with InnoDB storage engine

5.6.x with InnoDB storage engine

Oracle

10g/11g

Microsoft SQL Server

2008, 2008 R2, 2012, 2012 R2, and 2014

Note:
  • Before installing Command Center to work with an MS SQL Server database, ensure that you select the SQL Server Authentication mode when installing the database. The Windows Authentication mode is not supported in Command Center.
  • MSSQL2005 is not supported if you are installing CC 5.2 build 43.19. However, if you are upgrading to the CC 5.2 build 43.19 service pack build, MSSQL2005 is supported.

Additional Linux Requirements

Updated: 2013-07-22

The following are the prerequisites for installing Command Center on Linux.

You must ensure that the hostname -i command on the system on which Command Center is installed resolves the actual IP address and not the loopback IP address (127.0.0.1). If the hostname -i command does not resolve the actual IP address, do the following:

  1. Log on as root, and change to /etc directory.
  2. Open the host file using a vi editor.
  3. Update the line 127.0.0.1 localhost with the actual IP address, for example 10.102.41.10: 10.102.41.10 HostName
  4. For Linux ES 5.1, add the following line: 10.102.41.10 localhost

Client Requirements

Updated: 2014-08-04

The following table provides the minimum software recommendations for running the Command Center clients.

Browser

Version

Internet Explorer

IE 8, 9,10 and 11

Firefox

3.6.25 and above

Chrome

Latest

Safari

5.1.3 and above

Port Settings

This section covers the various ports that Command Center uses. The Command Center client and server use either HTTP or HTTPS to communicate. The HTTPS communication mode is enabled by default when you install the Command Center server.

The following table lists the ports used by the Command Center client and server to communicate with each other.

Purpose

TCP Ports

HTTPS communication between Command Center client and server.

8443

HTTP communication between Command Center client and server.

9090

Communication between Command Center High Availability (HA) servers.

6011, 2014, and 1099

 

The following table lists the ports used by the Citrix Command Center server to communicate with the Citrix NetScaler, NetScaler SDX, and Citrix CloudBridge.

Purpose

Port

SNMP communication between the Citrix Command Center server and the Citrix NetScaler system and Citrix CloudBridge.

161 (UDP port)

Configuration of SNMP traps between the Command Center server and the Citrix NetScaler system.

162 (UDP port)

SSH and SFTP communication between the Command Center server and the Citrix NetScaler system.

22 (TCP port)

HTTPS and HTTP communication between the Command Center server and Citrix CloudBridge.

443 and 80 (TCP ports)

HTTPS communication between the Command Center server and NetScaler SDX.

443 (TCP port)

Note: In the Command Center client, by using the Invoke Configuration Utility option, you can access the Citrix NetScaler utilities, such as the configuration utility and dashboard. To access the configuration utility and dashboard from Command Center, you must ensure that these are independently accessible from the client machine.

 

The following table lists the ports used for communication between the Command Center server and the Command Center agents.

Purpose

Port

Communication between the Citrix Command Center server and the Citrix Command Center agents.

Note: This port should be opened on the server as well as on the agents.

1099

Remote Method Invocation (RMI) lookup.

Note: This port should be opened on the server as well as on the agents.

6011

HTTPS communication between the Command Center server and the agents.

8443

HTTP communication between the Command Center server and the agents.

9090

Database Settings

Updated: 2014-12-23

Command Center supports the following databases:

After installing the database, you must configure the database user permissions and database parameters.

Database Parameters

The following table lists the parameters that you need to specify for the database settings.

Parameter

Description

Database

MySQL, Oracle, or MS SQL Server.

Host Name

IP address of the server or the server name where the database is hosted.

Port

Port number of the server where the database is hosted. The default port for MySQL is 3306, for Oracle is 1521, and for MS SQL Server is 1433.

Database Name

Name of the database.

SID

Name of the Oracle database.

User Name

Database logon user name. The default user for MySQL is root, for Oracle it is system, and for SQL Server it is sa.

However, the administrator can create users and define the required permissions. For information on the user permissions, see the section "Database User Permissions."

Password

Password assigned by the database administrator.

Note: Before performing a complete installation of a new version of Command Center, you must check for and uninstall earlier versions of Command Center.

Database User Permissions

After you have created the Command Center database and the database user, you need to grant the required permissions as described in the following table.

Database

User Permissions

Oracle

GRANT CREATE SESSION to DatabaseUserName;

GRANT CREATE TABLE to DatabaseUserName;

GRANT ALTER DATABASE to DatabaseUserName;

GRANT UNLIMITED TABLESPACE to DatabaseUserName;

GRANT CREATE TRIGGER to DatabaseUserName;

GRANT CREATE SEQUENCE to DatabaseUserName;

MS SQL

In the MS SQL Server Management tool, you need to set the following permissions:

  1. Click Security > Logins, and then double-click DatabaseUserName.
  2. In General, set Default database as the Command Center database.
  3. In User Mapping, under Users mapped to this login, select the default database, and under Database role membership for, select the db_owner role membership. Note that the public role is selected by default.

MySQL

GRANT ALL ON DatabaseName.* TO DatabaseUserName@ CommandCenterIPAddress identified by 'DatabaseUserPassword';

GRANT FILE ON *.* TO DatabaseUserName@ CommandCenterIPAddress identified by 'DatabaseUserPassword';

GRANT SELECT, UPDATE on 'mysql'.'user' TO 'DatabaseUserName'@'CommandCenterIPAddress';

GRANT RELOAD, PROCESS ON *.* TO DatabaseUserName@CommandCenterIPAddress;