The list of issues that are fixed in builds that were released prior to Build 42.7.
• The sorting option after performing a search under the Monitoring tab does not work.
[From Build 40.1] [#429631]
• On the Administration tab, after you configure the access setting values for server protocol and server port, and then upgrade Command Center, the values are reset to default server protocol and server port.
[From Build 40.1] [#407104]
• The SoftwareUpgrade task fails to upgrade CloudBridge appliances.
[From Build 40.1] [#435675]
• You might not be able to configure a high availability (HA) setup after upgrading a Command Center hardware appliance to version 5.1 build 33.3.
[From Build 40.1] [#446983]
• On a Command Center hardware appliance version 5.1 build 33.3, a failover can cause the MYSQL replication to fail, which in turn can disable high availability (HA)
functionality.
[From Build 40.1] [#451089]
• You cannot modify the device profile from Citrix Network > Add Device > Modify icon.
[From Build 40.1] [#366507]
• Huge NetScaler configuration files causes high disk usage.
[From Build 40.1] [#443441]
• After you upgrade Command Center, you cannot change the Command Center password.
[From Build 40.1] [#452151]
• You might not be able to configuring a high availability (HA) setup after changing the password of a Command Center hardware appliance.
[From Build 40.1] [#452506]
• On the Configuration tab, the task specific execution log does not display the Command Center user details.
[From Build 40.1] [#451621]
• If you use the Command Center graphical user interface (GUI) to change the database password for a high availability (HA) setup, the password change is not propagated to the secondary Command Center.
[From Build 40.1] [#458009]
• If you add a device on Command Center, the Device Profile drop-down list does not display all the available device profiles.
[From Build 40.1] [#460486, #461822]
• On the Configuration tab, when you add or edit a custom task, and click Add Command to add a command, the Command field displays very long commands in a single line and does not provide the scroll option.
[From Build 40.1] [#451367]
• On the Configuration tab, when you edit a custom task and click Add Task Variable to add a variable task, some fields are not displayed.
[From Build 40.1] [#451390]
• The Monitoring tab might not display the list of polled entities for a NetScaler HA pair.
[From Build 40.1] [#461609]
• When a secure FTP to a NetScaler device fails, an OutOfMemory (OOO) error occurs.
[From Build 41.14] [#381157, #462974]
• Event severity configuration changes roll back to their default configurations after a service pack installation.
[From Build 41.14] [#203098]
• When you generate a technical support file, the size of the stdout.txt file increases, causing an Out Of Memory (OOM) condition. As a result, Command Center fails to generate the technical support files.
[From Build 41.14] [#450086]
• If the licensing server fails, you cannot log on to Command Center.
[From Build 41.14] [#454501]
• An IE9 browser displays long overlapping commands in the ConfigurationChangeHistory built-in audit policy reports.
[From Build 41.14] [#464370]
• The refresh button on the Citrix Network > Maps page does not work.
[From Build 41.14] [#465180]
• In Command Center 5.2, you cannot modify the custom logs, such as ccapiout.txt, ccapierr.txt and ccagentout.txt.
Fixed Issues in Previous 5.2 Builds
32
[From Build 41.14] [#465802]
• If you upgrade Command Center to version 5.2, build 40.1, the SNMP community setting might become a blank string.
[From Build 41.14] [#470841]
• If you click on the Monitoring tab, Command Center throws an undefined error.
[From Build 41.14] [#474504]
• You can create duplicate groups through the 'Add Users' option.
[From Build 41.14] [#477690]
Fixed Issues in Previous 5.2 Builds
33
34
FAQs
Answers to frequently asked questions about Command Center are available in the following categories:
• General
• Installation & Setup
• Administration
• Citrix Network
• Configuration
• Fault
• Reporting
• Command Center Appliance
35
General
Q: How do I verify that Command Center service has started properly?
A: To verify that the Command Center service has started properly, you can do one of the following:
• Windows operating system: In Window Service console, see the status of the service.
• Linux: Use the /int.d/NSCCService status command to verify that the service has started.
• You can also check the status of the service in the logs/wrapper.log file. Verify that the following log entry is present at the end of the file "Please connect to web client using port <port number>."
Q: I am not able to connect to the Command Center client. What are the possible causes ? Possible Cause: Command Center service has not started properly.
Action: Check to see if the Command Center service is started. If not, start the service.
Possible Cause: You have not presented valid root-user credentials.
Action: Provide the correct credentials. If the error occurs even with the correct credentials, shut down the server and check the securitydbData.XML file. If it is empty, reinitialize the database.
Possible Cause: If the PostgreSQL service has not started, the Command Center service does not start.
Action: In wrapper.log file, if you see a " PostgreSQL doesn't start in timely fashion"
entry, start the PostgreSOL service first and then start the Command Center server.
Possible Cause: To access the Command Center client, you are using Internet Explorer with compatibility mode enabled.
Action: Disable compatibility mode, and then access the client.
Other possible causes :
• You are using host name that contains an underscore special character.
• The Command Center client is running with a NATed IP address.
• The Firewall is blocking the ports required by Command Center. If the firewall is enabled, disable it or unblock the ports needed for communication with the client.
• The connection to the database has been lost. To check, view the log entry in the logs/wrapper.log file.
• The host name used to access the Command Center server does not resolve to the Command Center IP address.
• The browser cache was not cleared after an upgrade.
• The port you are using to access the client has been modified from the default (Https 8443 or Http 9090).
Q: I am not able to access the user interface of the secondary Command Center over port 8443.
A: You can only access the primary Command Center through the GUI when configured in HA mode. The secondary Command Center only monitors the state and is not accessible through GUI.
Q: Can Command Center be monitored through any SNMP Manger?
A: Yes, since Command Center behaves as an SNMP agent on port 8161, any SNMP manager can contact Command Center through this port. Command Center can be monitored by loading NS-CC-MIB, which is in the <CC_Home>/mibs folder on any SNMP manager.
Q: Do I need to add Command Center agent as a trap destination on the devices managed by Command Center agent ?
A: No. Command Center server adds its IP address as a trap destination in the discovered devices. Command Center Agent does not add itself as a trap destination but only does the performance data collection, syslog, and entity monitoring. Traps are still handled by the Command Center server.
Q: How do I change the default ports used by Command Center ?
A: You can change the default port (8443 or 9090) to any standard TCP port by modifying the Server Port details in the Administration > Settings > Access Settings window. The changes in access settings are effective only after a restart.
Q: Can I back up and restore data?
A: You can do a data backup and restore only on a Command Center appliance.
Q: Is a license required for evaluation-mode installation of the software version of command center?
A: No.
Q: I am not able to log on to the Command Center server. Where can I view the current Command Center version?
General
36
A: You can find the version information in the
<CCHome>/conf/AboutDialogProps.xml file.
Q: Which Oracle JDBC driver version does Citrix Command Center use?
A: Command Center uses Oracle JDBC Driver version 10.2.0.3.0.
Q: What databases does Command Center support?
A: For detailed information about supported databases, see
http://support.citrix.com/proddocs/topic/command-center-51/cc-install-plan-installation-con.html.
Q: Does Command Center support any database resiliency solution, such as mirroring, or any other replication methods that I can consider implementing?
A: You can replicate a MySQL database in Command Center. Use Command Center in an HA setup with MySQL two-way replication.
Q:Can I configure ciphers on Command Center?
A: Yes, you can configure ciphers on Command Center.
A Command Center server or an appliance ships with a set of predefined ciphers. The default ciphers which are supported by Command Center are:
ECDHE-RSA-AES256-GCM-SHA384,ECDHE-RSA-AES128-GCM-SHA256,DHE-RSA-AES256-GCM-SHA To use ciphers other than the predefined cipher, you have to explicitly define them in the server.xml and transportProvider.conf files.
To configure a cipher
1. Open server.xml file located in the path <CC_HOME>\apache\tomcat\conf\backup, and include one or more ciphers as follows:
<CIPHERSUITES>ECDHE-RSA-AES256-GCM-SHA384,ECDHE-RSA-AES128-GCM-SHA256
</CIPHERSUITES>
General
37
Figure 1. Server.xml
2. Open transportProvider.conf file located in the path CC_HOME>\conf, and include one or more ciphers as follows:
<CIPHERSUITES>ECDHE-RSA-AES256-GCM-SHA384,ECDHE-RSA-AES128-GCM-SHA256
</CIPHERSUITES>
Figure 2. TransportProvider.conf General
38
39