CA Performance Center Readme 2.4

1.0 CA Spectrum Support and Upgrade Considerations

If you plan to register a CA Spectrum data source with CA Infrastructure Management 2.4, we recommend upgrading to CA Spectrum Release 9.4. Earlier versions of CA Spectrum do not fully support the following new features:

• Synchronization of CA Performance Center IP domains in CA Spectrum
• Global collection and landscape synchronization
• Drilldown capabilities from device and interface models in CA Spectrum OneClick to CA Performance Center performance data
• IP domain-aware synchronized discovery

Note: For information about upgrading CA Spectrum to Release 9.4, see the CA Spectrum Release 9.4 documentation.

1.1 Required Configuration for Large Deployments

Modify the configuration file for the CA Performance Center MySQL server in large-scale monitoring environments.

CA Performance Center installs MySQL with two default settings that are optimized for a medium-sized database. If you intend to run CA Performance Center on a system to support a large-scale deployment, modify the following two parameters from their default settings in the /etc/my.cnf file:

thread_concurrency = 8

key_buffer_size = 4096M

Take this step just after the installation has completed, but before you launch CA Performance Center for the first time.

When you have completed the changes to the my.cnf file, run the following command to restart MySQL:

/etc/init.d/mysqld restart

Recommendations

Set the thread_concurrency parameter to equal twice the number of CPUs on the target system.

Set the key_buffer_size to about 12 - 15% of total memory on the system.

For more information, see the MySQL documentation at http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html

1.2 Upgrade Steps to Support HTTPS (SSL)

When you upgrade to CA Performance Center 2.4, a few steps are required to enable Single Sign-On support for SSL encryption (HTTPS).

Note: These steps are only required if you had HTTPS configured in Single Sign-On for the previous release of CA Infrastructure Management. Otherwise, follow the steps that are provided in the Single Sign-On User Guide to configure HTTPS.

After the upgrade, the certificate that was previously imported to the Jetty keystore and to the Java keystore is not imported to the new keystores. Take some steps to import the certificate.

Follow these steps:

1. Copy the keystore from the old Jetty directory to the new Jetty directory:

   cp $InstallDir/PerformanceCenter/jetty-7.2.0/etc/keystore $InstallDir/PerformanceCenter/jetty/etc

2. Import the certificate to the new Java keystore. The steps are different if you are using a certificate from a Certificate Authority (CA) or using a self-signed certificate.

   If you are using a CA certificate:

   • Import the signed CA certificate to the Java keystore:

     cd $InstallDir/jre/lib/security

     keytool -importcert -keystore cacerts -storepass keystorepwd –alias alias -file CACertFile

   If you are using a self-signed certificate:

   • (Optional) Export the certificate (unless you already have it):

     cd $InstallDir/PerformanceCenter/jetty/etc/keystore

     keytool –export–alias alias -keystore keystore –rfc –file {$OtherDir}/alias.cer

   • Import the file (alias.cer) to the Java keystore.

     cd $InstallDir/jre/lib/security

     keytool –importcert –keystore cacerts –alias alias -file {$OtherDir}/alias.cer –storepasskeystorepwd

3. Restart the following services:
   • caperfcenter_sso
   • caperfcenter_console
   • caperfcenter_devicemanager

1.3 Maintain Functionality with Concurrent Users

Symptom

When you upgrade to CA Performance Center 2.4, the following pages are slow to load under high event load and high user load:

• Events Display
• Device Details Tab
• Interface Details Tab

Note: This issue does not exist in Releases 2.4 and later.

Solution

Insufficient database connections that are allocated to the Event Manager cause this issue. As a result, the Event Manager cannot handle multiple large simultaneous queries. Increase the maxActive attribute in the em.properties file.

Follow these steps:

1. Edit the file /opt/CA/PerformanceCenter/EM/webapps/EventManager/WEB-INF/em.properties.
2. Change the following attribute to 40:

   maxActive

3. Restart the Event Manager.

   /etc/init.d/caperfcenter_eventmanager restart

1.4 Replace Customization Files

Symptom

When you upgrade to CA Performance Center 2.4, customization that is done before the upgrade appears to be lost. However, the Data Aggregator saves the customization, and can retrieve it. You are unable to access the customization web application using <CAPC_HOSTNAME>:CA Portal/ems.

Solution

Copy the file "$EMS_INSTALLER/core/MediationUtil/ems.war" to the $CAPC_INSTALL_DIR/PC/webapps directory.

1.5 Nonfatal Errors in Installation Log

After you upgrade to CA Performance Center 2.4, the following two errors appear in the installation log:

Fail to determine version: Failed to compare current version: 5.5.1d against installed version: null

Execute Custom Code

class com.ca.im.dm.core.installer.CustomCode.config.CanInstallAfterBackup.install() runtime exception: java.lang.IllegalArgumentException: does not exist

The errors do not affect the upgrade in any way. You do not need to act. The upgrade installs correctly.

1.6 Migrate Devicepacks between Data Collectors

Too many devicepacks deployed in a single Data Collector can affect performance negatively. To improve performance, you can migrate selected device packs to another Data Collector.

NOTE: If you are migrating only the Engine, skip step 5. Verify that PRESENTER_ID of the OLD server matches the PRESENTER_ID of the Engines.

1. Install a Local Controller (LC) on the new server, and point to the appropriate Multi Controller (MC) server during the installation.
2. After LC is successfully installed on the new server, verify that CAMM WEB shows two LCs on the Hosts page at the following URL: http://<CAMM_MC_Servername>:<CAMMWEBPORT>/tim-web/index.htm
3. Stop the Engines and Presenter that are associated with the old server.
4. Log in to CAMM WEB and deploy the device pack engines to be migrated. Verify that new server is selected as LC.

   Example: If the old server has Engine_CAAlcatel5620Sam, then provide Engine_CAAlcatel5620Sam_<NEW_SERVER_IP>.

5. Deploy the Presenter from CAMM WEB, and verify that the new server is selected as LC.

   When you deploy, provide a different component ID of the Presenter other than the one in the old server.

   Example: If the old server has the component id PRESENTER_CAPM, then provide PRESENTER_CAPM_<NEW_SERVER_IP>.

6. Log in to the MC server, and navigate to the following directory:

   $CAMM_INSTALL/MC/repository/<OLD_SERVER_IP>/COMPONENTS

7. Execute the following command:

   cp –R ENGINE_<devicepack>/* $CAMM_INSTALL/MC/repository/<NEW_SEVER_IP>/COMPONENTS/ENGINE_<devicepack_NewID>/

8. If the devicepack to be migrated uses the sftp/ftp/copy mechanism as a data acquisition method, then:
   1. Create the following directories under NEW_SERVER:

      $CAMM_INSTALL/COMPONENTS/ ENGINE_<devicepack_NewID>

      $CAMM_INSTALL/COMPONENTS/ ENGINE_<devicepack_NewID>/tmp/input/inventory

      $CAMM_INSTALL/COMPONENTS/ ENGINE_<devicepack_NewID>/tmp/input/performance

   2. Copy the following files from OLD_SERVER to NEW_SERVER:

      $CAMM_INSTALL/COMPONENTS/ENGINE_<devicepack>/tmp/input/inventory/.historyFile.Inventory to $CAMM_INSTALL/COMPONENTS/ ENGINE_<devicepack_NewID>/tmp/input/inventory

      $CAMM_INSTALL/COMPONENTS/ENGINE_<devicepack>/tmp/input/performance/.historyFile.Performance to $CAMM_INSTALL/COMPONENTS/ ENGINE_<devicepack_NewID>/tmp/input/performance

9. Start the Engine and Presenter that are associated with the new server.

2.0 Known Issues

2.1 Interface Domain Changes

When an administrator allocates the interfaces from a single router to multiple MSP customer domains, interfaces are often switched to different IP domains. CA Network Flow Analysis detects interface domain changes. These changes are not applied to data being sent to Data Aggregator, however, because Data Aggregator only identifies interfaces at the device level.

As a result, when interfaces are switched to a different domain after monitoring and data collection have begun, the global administrator sees two different interface items in CA Performance Center for each affected interface. The two interfaces continue to be monitored in separate IP domains, and their data is not aggregated. In this situation, individual tenant users do not see any problem. Device-level statistics for the routers or switches that contain these interfaces are not affected. Only the global administrator sees two interfaces to represent a single monitored interface.

2.2 Event Manager Limitations

Notifications

In this release, Event Manager notifications only respond to events coming from Data Aggregator or CA Network Flow Analysis.

When you are sending Event Manager traps using the Notifier, you can send them in either of two trap (MIB) formats: the nhLiveAlarm format or the EventManager format. However, CA eHealth events are not supported, so you cannot create event notifications for a CA eHealth data source. EventManager is the recommended format. The nhLiveAlarm format is provided for users who already have a trap receiver that is customized to receive traps in the CA eHealth format.

Supported Data Sources

Event Manager relays data and displays events from the following data sources:

• CA Application Delivery Analysis
• Data Aggregator
• CA Network Flow Analysis
• CA Unified Communications Monitor

Events Display Limitation

The CA Performance Center Events list view is limited to show a maximum of ten pages of events. This design preserves user interface performance in large-scale environments. If your large deployment has 10,000 events for the selected time period, the dashboard shows only ten pages of ten events. A message indicates that only 100 events are shown.

A workaround lets you see more events by changing the Max per page setting at the bottom of the Events list view. You can select 50 or 100 as the maximum number of events to include on each page and can scroll through more events. However, the limit of ten pages maximum is still enforced.

2.3 Commas in IP Domain Definitions

The use of commas (,) in your IP domain definitions is not supported.

3.0 Localization Known Limitations

A full list of anomalies associated with translation is provided in the Localization Status Readme file.

3.1 Double Byte Language Characters Can Display Incorrectly in PDF Reports

If you generate a PDF report in a language that uses double byte characters (for example, Chinese, Simplified Chinese, or Japanese), characters can display incorrectly. Characters can display incorrectly for two possible reasons:

• You do not have an installed font that supports the language.
• The licensing bit for the font is set in a form that cannot be embedded in PDFs.

To resolve this issue, do one or more of the following steps:

• Install a font that supports the language you want to generate a PDF in.
• Be sure that the fonts you have installed can be embedded in PDFs. The following fonts, available on computers that are running a Windows platform, can be installed on a computer that is running a Linux platform. These fonts can be embedded in PDFs:
  • MS GothicUI
  • MeiryoUI
  • SimSun

3.2 Bookshelf Versions and Translations

The CA Network Flow Analysis Documentation Bookshelf is included with the CA Performance Center user interface. In addition to English, it is also available in three languages, but it is not available in Traditional Chinese.

The CA Application Delivery Analysis documentation is not available in French. However, translated versions of the CA Application Delivery Analysis online Help for CA Performance Center are available in Simplified Chinese and Japanese.

4.0 Data Source Known Issues

4.1 Limitations in Data Source Support for Multi-Tenancy Features

Support for multi-tenant monitoring in CA Performance Center is subject to some limitations in the registered data sources. Where a Data Aggregator data source has fully implemented multi-tenancy and IP domain monitoring, the following data sources offer more limited support:

• CA Application Delivery Analysis
• CA Spectrum
• CA eHealth
• CA Application Performance Management

CA Application Delivery Analysis monitors IP domains without a concept of tenants. As a result, CA Performance Center receives all items from CA Application Delivery Analysis in the Default Tenant. However, CA Application Delivery Analysis does support IP domains. CA Performance Center can thus associate these items with tenants according to their IP domain. Be aware that some managed items are duplicated between the Default Tenant and custom tenants.

Starting with r9.3, CA Spectrum supports custom IP domains. CA Spectrum devices can be placed in custom IP domains or in the Default IP Domain. Tenants are not visible in CA Spectrum OneClick. However, tenants in CA Performance Center can have associated CA Spectrum devices based on IP domain. The global administrator can also make these items available for monitoring by tenant users by placing them into the Service Provider Items group. For more information, see the CA Spectrum - CA Performance Center Integration Guide.

With the CA Network Flow Analysis, CA Application Delivery Analysis, and CA Unified Communications Monitor data sources, segregation by tenant ends at drilldown into the data source user interface. You can use Product Privilege settings and role rights to prevent tenant users from seeing data from other tenants. For more information, see the use case titled "Deploying Multi-Tenancy with CA Performance Center."

Neither CA eHealth nor CA Application Performance Management supports IP domains or tenants. Therefore, all items and configuration that are contributed by these data sources are visible only in the Default Tenant and in the Default IP Domain.

4.2 Interface Display for Users of CA Network Flow Analysis

Interface names and descriptions may not match between the NFA console and the CA Performance Center Console.

Note: Changes to the interface names and descriptions are limited to the product that you use to make the changes. If you change interface descriptions in one product console, the changes are not displayed in the other console, for example. To show the same interface names and descriptions in both locations, make revisions in one product to match the other product.

NFA Console

• The interface name and description is formatted as defined by the interface template, which uses the following values by default:
  • Interface Name: ifName or ifDescr value, whichever is found first
  • Interface Description: portName or ifAlias value, whichever is found first

  For information about changing the default template behavior, see the CA Network Flow Analysis topic 'Edit the Interface Template.'

• To customize interface names and descriptions individually, use the Active Interfaces page. For more information about this task, see the CA Network Flow Analysis topic 'Edit Details for a Router, Interface, or CVI.'

  Any changes you make are shown in a number of locations, including the Active Interfaces page, Enterprise Overview reports, drilldown Interface page reports, and the Interface Index. You use the Interface Index to select interfaces as filters in Custom reports and Analysis reports and to navigate to an interface in the Interface pages.

CA Performance Center Console

• The CA Performance Center Interface Details, Inventory pages, and trend views display interface names and descriptions that use the following default values:
  • Interface Name: ifName, ifDescr, or "Interface {ifIndex}" value, whichever is found first
  • Interface Description: ifDescr value, unless you apply an Interface Description Override to the parent domain
• To customize interface descriptions, apply an Interface Description Override when you create a domain, as described in the CA Performance Center topic 'Add an IP Domain.' To change the Interface Description Override settings for an existing domain, complete the following steps:
  1. Prepare a .csv file with the interface description overrides that you want to use. Include the following columns and populate a row for each interface whose description you want to override: Device IP, Name, Description, and Interface Description Override.
  2. Log in to the CA Performance Center Console as a user with administrator privileges.
  3. Select Admin, IP Domains.

     The Manage IP Domains page opens.

  4. Select the domain that you want to edit.
  5. Click Edit.

     The IP Domains Administration dialog opens.

  6. Click Browse next to the Interface Description Override field.
  7. Locate and select the .csv file that contains the appropriate overrides.
  8. Click Save in the IP Domains Administration dialog.

     The dialog closes.

  9. Resynchronize the CA Network Flow Analysis data source:
     1. Select Admin, Data Sources from the console menu bar.

        The Manage Data Sources page opens.

     2. Select the CA Network Flow Analysis data source.
     3. Click Resync.

        The data source is resynchronized.

     Note: You can wait 5 minutes for the next synchronization to complete automatically instead of resynchronizing manually.

  10. Verify that the overrides have been applied in the Interface Details page, Inventory pages, and trend views.

The interface descriptions apply to devices that have already been discovered and to devices that will be discovered in the future.

4.3 New Column in the Call Quality SLA View is Not Supported for Previous Versions of the Data Source

The Call Quality SLA view from the CA Unified Communications Monitor data source includes a "Calls Not Meeting SLA" column. The new column is supported only by CA Unified Communications Monitor data sources at version 3.5 or later. This release of CA Performance Center will return an error if it sends a request for the new data to a CA Unified Communications Monitor data source that is not at version 3.5 or later.

4.4 Search View Filter Does Not Work for Unified Communications Views

The Search View filter may not function for the views in the Unified Communications dashboards.

5.0 Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

• Online and telephone contact information for technical assistance and customer services
• Information about user communities and forums
• Product and documentation downloads
• CA Support policies and guidelines
• Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

Copyright © 2014 CA Technologies. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.