Release Notes

Summary of enhancements, fixes, and open issues
camm212
Contents
21.2.4 New Features and Enhancements
This release of
DX NetOps Mediation Manager
includes the following new features and enhancements.
Support for Tomcat 8.5.71
This release contains the support for Tomcat 8.5.71 to address the security vulnerabilities.
Disabled Autocomplete Passwords
Starting from 21.2.4, AutoComplete for Passwords is disabled while Form-Based Authentication.
21.2.2 New Features and Enhancements
This release of
DX NetOps Mediation Manager
includes the following new features and enhancements.
Support for IPv6
From this release of
DX NetOps Mediation Manager
, installation on the IPv6 host is supported. The following points are to be considered to use
DX NetOps Mediation Manager
on IPv6 host.
  • As a prerequisite to use this feature, you must upgrade the infrastructure from IPv4 to IPv6. After the infrastructure upgrade, fresh installation of DX NetOps Mediation Manager is recommended.
  • You can install or upgrade the
    DX NetOps Mediation Manager
    on the IPv6 infrastructure. While upgrading from IPv4 infrastructure to IPv6 infrastructure, perform the following post-upgrade steps
    1. Prepare the
      ipv4Toipv6MappingFile
      file in the following format:
      You can create this file in any local drive location.
      <IpV4_address>=<IpV6_address> Example: 127.0.0.1=0:0:0:0:0:0:0:1 10.80.112.218=fddb:fe2a:ad1e:0:0:0:c0a8:1
      IpV6_address must be in full form
    2. Run the
      dxmmUpgradeIpv4ToIpv6
      script from the
      /opt/CA/CAMM/tools
      location.
      You must provide the absolute path of the
      ipv4Toipv6MappingFile
      file while running the script.
      ./dxmmUpgradeIpv4ToIpv6 <ipv4Toipv6MappingFile_with_absolute_path >
    Post upgrade scenarios
    • If
      DX NetOps Mediation Manager
      is installed with a hostname in IPv4 infrastructure, then perform the post-upgrade steps in primary MC and secondary MC hosts.
    • If
      DX NetOps Mediation Manager
      is installed with an IPv4 Address in IPv4 infrastructure, then perform the post-upgrade steps in primary MC, secondary MC, and all LC hosts.
    • If
      DX NetOps Mediation Manager
      is installed with a combination of hostname and IPv4 Address in IPv4 infrastructure, then perform the post-upgrade steps in primary MC, secondary MC, and all LC hosts.
  • The local host address for IPv6 is ::1.
  • SFTP and HTTP plugins support IPv6 to collect data from EMS.
  • If the infrastructure supports dual stack (i.e. both IPv4 and IPv6) and DX Mediation manager is installed on IPv6, then the CAMMWEB can be launched using the following URLs:
    http://<HostName>:<web-port> http://<PrimaryMCMachineIPv6>:<web-port> http://<PrimaryMCMachineIPv4>:<web-port>
For the engine data collection using http plugin, you must provide the hostname instead of the IPv6 address in the engine configuration.
21.2 New Features and Enhancements
This release of
DX NetOps Mediation Manager
includes the following new features and enhancements.
Enable HTTPS for DX NetOps Mediation Manager
You can now configure
DX NetOps Mediation Manager
with HTTPS for secure connections.
For more information, see Configure DX Mediation Manager to Use HTTPS.
Enhancements
  • Existing CACiscoCallManager device pack is enhanced to support the SNMP reconciliation.
  • Enhanced the device pack to support multiple call managers and its metrics support.
  • Mediation Manager is enhanced to connect and deploy Certs over DA using credentials.
Known Issues
The following are the known issues for
DX NetOps Mediation Manager
21.2:
  • The device pack does not appear in
    NetOps Portal
    2.7 and later version.
    This issue occurs when you upgrade CA Performance Management from 2.6 or lower version to 2.7 and later version but use CA Mediation Manager 2.6 or lower version.
    To resolve this issue, follow these steps:
    1. Log in to Mediation Manager after you upgrade to version 21.2, and click the
      Device Packs
      tab.
    2. Select the subcomponent
      PRESENTER_CAPM
      ,
      and click
      Stop.
    3. Ensure that the
      PRESENTER_CAPM
      is selected, and click AdvancedAdvanced icon.
      The PRESENTER_CAPM
      window appears
      .
    4. Click
      Configuration
      on the right pane.
    5. Update the value in
      OUTPUT_DIRECTORY
      as follows:
      /opt/IMDataCollector/apache-karaf-4.2.6/MediationCenter/
    6. Click
      Save
      ,
      Close
      .
    7. On the Device Pack window, select
      PRESENTER_CAPM,
      and click
      Start
      .
    This issue can also occur if Mediation Manager is upgraded from version 2.7 to version 21.2 but
    PRESENTER_CAPM
    is not upgraded. In that scenario, either upgrade PRESENTER_CAPM or manually modify the OUTPUT_DIRECTORY value as specified in step 5.
  • CA Mediation Manager 2.4, 2.5, 2.6, 2.7, and 2.8 fail to deploy device pack certificates in CA Performance Management 3.0 or later.
    This is a compatibility issue. To resolve this issue, upgrade CA Mediation Manager to version 3.0 or later because Mediation Manager 2.4 through 2.8 are not compatible with CA Performance Management 3.0 or later.
    For more information about the known interoperable combinations of DX NetOps components and data sources for this release, see DX NetOps Interoperability.
  • DX NetOps Mediation Manager
    on Windows and Solaris Supports only Multi-Controller
    Even if the
    DX NetOps Mediation Manager
    Local Controller is installed on Windows and Solaris, you must manually copy the Queue folder (where the input files get collected) to the Data collector.
  • CAAVIController device pack supports single AVI Controller
  • CERT deployment fails when the corresponding CERT folders are zipped at the parent level
    The CERT deployment fails when the following folders are zipped at the parent level (CERT_<DevicePack_Name>).
    • components
    • device_mapper
    • metric_families
    • vendor_certs
    As a workaround, ensure that you zip the preceding four folders.
  • While installing
    DX NetOps Mediation Manager
    in the Windows environment, make sure that the JRE path should be an environment variable with JAVA_HOME name and bin directory of JRE shall be in the path.