DX NetOps Mediation Manager for Performance Management

DX NetOps Mediation Manager for Performance Management
2-5
Contents
Architecture, Components, System Requirements
  1. How to distribute Primary MultiController, active LocalController, and a standby LocalController in a multiserver installation?
    Install Primary MultiController and an active LocalController with Engine and Delivery Service in one system. A standby LocalController can be installed in any system that has sufficient RAM and CPU spaces. The following diagram shows one of the possible scenarios:
    DX NetOps MM for PM with 5 systems
    CAMM for PM with 5 systems
  2. Is it mandatory to install Primary MultiController in the system that has CA Performance Center?
    No. Install the Primary MultiController in the system that has CA Performance Center only if it has enough memory to accommodate new device packs and MultiController.
  3. Is there a system requirements guideline to install DX NetOps Mediation Manager for Performance Management?
    Refer to the Sizing Guidelines document available at the CA Support site.
  4. How can I improve the performance of CAPM Presenter?
    The number of CAPM Presenters that are required for your environment depends on the number of complex device packs that you intend to deploy. If the amount of data to be processed is very large, the performance of a CAPM Presenter can be impacted. In such deployments, install multiple CAPM Presenters. In DX NetOps Mediation Manager, you can use the same installation file of a subcomponent and can install multiple subcomponents by changing the name of the subcomponent. Therefore, install multiple CAPM Presenters by using the same Presenter zip file, which is created after migrating the device pack. Similarly, install multiple Engines and provide the path of the corresponding CAPM Presenter and host names.
    Example 1:
    To collect data from nine hosts (named H1 through H9), install multiple Engines and CAPM Presenters, and distribute the host names accordingly. One of the scenarios is as follows:
    • Engine 1 contacting CAPM Presenter 1 and Hosts: H1, H2, and H3
    • Engine 2 contacting CAPM Presenter 2 and Hosts: H4, H5, and H6
    • Engine 3 contacting CAPM Presenter 3 and Hosts: H7, H8, and H9
    Example 2:
    • Engine 1 contacting CAPM Presenter 1 in Data Collector 1 and Hosts: H1, H2, H3, H4, and H5
    • Engine 2 contacting CAPM Presenter 2 in Data Collector 2 and Hosts: H6, H7, H8, and H9
      All three Engines are of the same device pack but have different COMPONENT_ID parameters. All three CAPM Presenters are installed from the same zip file and have same COMPONENT_IDs as their Engine.
Scripts to start, stop, and check the status of the components
  1. How do I start, stop, or check the status of the CA Performance Center services?
    Execute the following commands to stop the services:
    /etc/init.d/caperfcenter_console stop; /etc/init.d/caperfcenter_eventmanager stop; /etc/init.d/caperfcenter_devicemanager stop; /etc/init.d/caperfcenter_sso stop;
    Execute the following commands to start the services:
    /etc/init.d/caperfcenter_devicemanager start /etc/init.d/caperfcenter_sso start /etc/init.d/caperfcenter_eventmanager start /etc/init.d/caperfcenter_console start
    Execute the following commands to check the status of the services:
    /etc/init.d/caperfcenter_sso status /etc/init.d/caperfcenter_devicemanager status /etc/init.d/caperfcenter_eventmanager status /etc/init.d/caperfcenter_console status
  2. How do I start, stop, or check the status of the Data Aggregator services?
    How do I start, stop, or check the status of the Data Aggregator services?
    Execute the following commands to start the services:
    /etc/init.d/dadaemon start
    Execute the following commands to stop the services:
    /etc/init.d/dadaemon stop
    Execute the following commands to check the status of the services:
    /etc/init.d/dadaemon status
  3. How do I start, stop, or check the status of the Data Collector services?
    Execute the following commands to start the services:
    /etc/init.d/dcmd start
    Execute the following commands to stop the services:
    /etc/init.d/dcmd stop
    Execute the following commands to check the status of the services:
    /etc/init.d/dcmd status
Device Pack Migration
  1. What are the options in migratePMtoCAMM and when do we use them?
    The options to execute migratePMtoCAMM are a, d, and t. Use these options under the following scenarios:
    d:
    To migrate the device pack before upgrading the Data Collector. However, do not start the device pack till the Data Collector is upgraded to release 2.3.4. Also, always use option “d” to migrate the CANECeNodeB, CACRBT, or CACRBTUSER device pack.
    t:
    To test the device pack that is generated in a DX NetOps Mediation Manager setup, in another DX NetOps Mediation Manager setup. You can also use this option to test the device pack that is generated in the lab environment before upgrading Performance Management in the production environment.
    a:
    To migrate the device pack and start the device pack immediately after migration. However, before you use this option confirm that the Data Collector is upgraded to release 2.3.4.
  2. Will there be any data loss after migration?
    No. If you are using DX NetOps Mediation Manager 2.2.6 and above in Performance Management 2.3.4, the migration script will handle the historical files and start processing after the point where the EMS Profile stopped.
  3. Why are there gaps in reports after executing the migration script?
    After the migration, there should not be gaps in the report. However, if there is no data from the EMS server at any time, gaps appear in the reports.
Notification Feature
  1. Where are the configuration files of the Notification feature available?
    The Notification feature is available starting
    DX NetOps
    release 2.5. If you install afresh or upgrade to the latest version, the configuration files for the Notification feature are added to the following location: <
    CAMM_Install_folder
    >/CA/CAMM/AD
  2. What is the folder structure for the configuration files of the Notification feature?
    All configuration files for the Notification feature are in the AD folder, which is in the <
    CAMM_Install_folder
    > location. The following diagram provides the list of other files and subfolders:
    Anomaly Detector Folders and Files
    Anomaly Detector Folders and Files
  3. What are the contents of the configuration files and their uses?
    AnomalyConfigBase
    Contains the following folders that has the anomaly files for each component and the xml file to generate emails:
      • MC_ANOMALY
      • LC_ANOMALY
      • Engine_ANOMALY
      • Presenter_ANOMALY
      • EmailConfig.xml
    <
    component
    >_ANOMALY
    <
    component
    > refers to MC, LC, Engine, or Presenter. By default, this folder contains two xml files: Rules.xml and Anomalies.xml. When you select an anomaly for a component in UI, <
    component name
    >_Rules.xml is created and it contains the anomalies with rules specified in the UI. According to the rules specified in UI, notification is sent. The <
    component name
    > refers to the component name in the UI.
    EmailConfig.xml
    Contains server properties details and email addresses that are specified in the Server Properties area in UI. This file is generated based on the EmailConfig_Template.xml file when you specify the parameters in Server Properties. Anomaly notification is sent to the email addresses added to this file.
    logs
    Contains log files that the Notification feature generates.
    template
    Contains template xml files to trigger test email, perform cleanup, and store the server properties and email addresses.
    LocalConfig-ad.xml
    Starts the Notification feature. This file also contains
    information about the default port number. Currently, the feature uses the port 29570. Therefore, ensure that the port is available for this feature. If the port 29570 is occupied and you want to allot different port for the Notification feature, stop the feature, change the port number in the LocalConfig-ad.xml file, start the feature, and change the port number in all other locations where
    DX NetOps
    components are installed.
    cleanup
    Contains xml file to perform the cleanup of the log files. You can change the log file cleanup by changing the appropriate parameters.
    .local
    Contains the jmxPort number and this folder is created when the feature is started. This port remotely monitors Java resources (CPU, Memory, Heap, and Number of Classes) of this feature.
  4. When I upgrade
    DX NetOps
    , will the email server properties and anomaly settings be lost?
    No.
  5. What happens to the selected anomalies when an Engine is moved from one LocalController to another LocalController?
    ENGINE_<
    devicepack
    >_Rules.xml is deleted and created again. In this process, the previously selected parameters are lost.
  6. How can I know the anomalies for which I will receive email notifications?
    Use one of the following methods to know the selected anomalies:
    • Through UI: In the My Settings, Notification area, expand the DX NetOps MM Components node and click a component. For the selected anomalies in the <
      component
      > Anomalies area, you receive notifications.
    • Through scripts: Execute the cammStatus -ad script from the <
      CAMM Install
      >/CA/CAMM/tools folder.
    • Through <
      component name
      >_Rules.xml:  See the rules which have selected=”true”.
  7. Can I change the anomalies name in
    the <
    component name
    > Anomalies area
    in UI?Yes. Follow these steps:
    1. Open the <
      component name
      >_Rules.xml file in the <
      component
      >_ANOMALY folder.
    2. Change the text in the name field.
      Example: In MC-Primary_Rules.xml, change "MC stopped" in the name field according to your choice.
    3. Save the file and exit.
  8. What are the parameters in the <
    component name
    >_Rules.xml file and which parameters can be changed?
    The details of the parameters in the <
    component name
    >_Rules.xml
    are as follows:
    asserted
    Indicates whether the anomaly is detected or not. Do not change this parameter.
    frequency
    Indicates the time interval according to which the rule is executed in the background. If anomaly is detected during the execution, email notification is sent.
    Units: Seconds
    id
    Specifies the component identifier. Do not change this parameter.
    name
    Specifies the
    anomaly name. This name appears in the Anomalies section in UI.
    selected
    Indicates whether the component is selected through UI for anomaly detection.
  9. How can I change input parameters of a rule that is used to detect an anomaly?
    Open the <
    component name
    >_Rules.xml file in the <
    component_name
    >_ANOMALY folder. In this file, except the asserted and id fields, you can update the other input parameters.
    Example:
    In PRESENTER_CAPM_Rules.xml, the DX NetOps MM DC Queue size growing anomaly, you can modify the setThresholdInPercentage and setMaxTrend input parameters.
  10. How do I stop
    DX NetOps
    to detect anomaly?
    In the Notification area, expand the DX NetOps MM Components node, click a component, clear the check box of the anomaly, and click Save.
  11. How to customize the test email message?
    Open the Test_Anomalies.xml file in the <
    CAMM_Install_Folder
    >/AD/Template folder and change the subject or title.
  12. How can I customize the troubleshooting and causes messages according to my environment?
    Open the Anomalies.xml file in the AD/AnomalyConfigBase/<
    component
    >_ANOMALY location and change the text.
  13. How to start and stop the notification feature?
    Execute the following script to start the feature:
    startall -c ad
    Execute the following script to stop the feature:
    stopall -c ad
  14. Can anomaly be detected even when the
    DX NetOps
    components are
    not running?
    Yes, unless the stopall script was executed to stop all services of
    DX NetOps
    .
  15. Is there any specific system requirements for the Notification feature to function?
    No.
  16. Can I use this feature to monitor anomalies in CA Performance Management?
    No.
  17. Can I use this feature if the primary MultiController is down?
    No. Do not change the settings through UI when the primary MultiController is down.
  18. What happens to the selected anomalies if an Engine is removed from my environment?
    All the anomalies that are selected for the Engine are deleted.
  19. Where is the log file for the Notification feature?
    In the <
    CAMM_Intall_Folder
    >/AD/logs location.
  20. How do I change the log levels for this feature?
    Open logging.properties from the <
    CAMM_Intall_Folder
    >/AD/logs location and change INFO to FINE/FINEST
  21. How to edit the default port number?
    Follow these steps:
    1. Stop the feature by executing the stopall -c ad script.
    2. Open LocalConfig-ad.xml from the <
      CAMM_Intall_Folder
      >/AD location.
    3. Change the port number in the LocalConfig-ad.xml file.
    4. Start the feature.
    5. Change the port number in all other locations where
      DX NetOps
      components are installed.
  22. How can I monitor the system resources used by this feature?
    Follow these steps:
    1. Install JDK 1.7 or above in a system where
      DX NetOps
      is running.
    2. Double-click jconsole.exe in <
      JDK_HOME
      >\bin to open JConsole.
    3. Select Remote Process in the JConsole New Connection dialog.
    4. Copy the JMX connection URL from the log file. Example: service:jmx:rmi:///jndi/rmi://127.0.0.1:10979/timJmxRmi
    5. Replace the “127.0.0.1” IP address with the actual IP address where the Notification process is running.
    6. Replace "10979" with the value in the jmxPort.xml file in the <
      CAMM_Install_Folder
      >/CAMM/AD/.local location.
    7. Type the login credentials and click Connect.
      JConsole displays the utilization details of “Memory”, “CPU”, “Threads” & “Classes”.