Known Issues

uim203
The following known issues are applicable for UIM:
2
Application is Vulnerable to Insecure Communication Vulnerability
Symptom:
User-specific sensitive authentication data is transmitted in clear text, which can be sniffed by an attacker to compromise users identity and obtain unauthorized access to the application.
Solution:
Use SSL on any authenticated connection or whenever sensitive data is being transmitted. Use SSL for all connections that are authenticated or transmitting sensitive or value data, such as credentials, credit card details, health, and other private information. Ensure that communications between infrastructure elements, such as between web servers and database systems, are appropriately protected via the use of transport layer security or protocol level encryption for credential's and intrinsic data.
CABI Installation Fails When Using Special Characters in Operator Console (OC) and LDAP Account Names
When you use special characters (\, |, [ ], `, ", ', ~, !, #, $, %, ^, &, [,], *, +, =, ;, * :, ?, <, >, }, {, ), (, ], [, /, @) in the Operator Console (OC) or LDAP account names, account synchronization with CABI fails which results in a failed installation.
Cannot Collect Non-Default QoS Metrics When Using Enhanced Templates
Symptom:
When using the enhanced templates, the probe configuration file is not updated with the QoS metric information.
Solution:
The QoS collection for default metrics works as expected for legacy templates. However, for enhanced templates, the probe configuration file is not updated as there is no mapping in the template for the non-default QoS collection.
CDM Probe Setting Might Impact the Performance of discovery_server When Monitored Devices Are Using a Shared File System
Symptom:
By default, the CDM Probe configuration has the Setup/allow_remote_disk_info set to Yes. This allows the CDM Probe to generate the Device ID for all shared drives on a monitored device using a shared file system. In this situation, cdm creates duplicate perspectives for the same shared file system. This can impact the performance of the discovery_server.
Solution:
To correct this issue, use Raw Configure to change the cdm Setup/allow_remote_disk_info set to No. Review the UIM database and remove duplicate perspectives. This should return the performance of the discovery_server to a normal operating level.
Deploying Probes on Dual Stack Mode (IPv4 and IPv6) Not Supported
Symptom:
When you run the Nimsoft Loader (nimldr) utility and configure the primary hub using IPv6 address and are running the dual stack mode, then one of the following occurs:
  • When an IPv4 address is given for the Primary Hub, then the installation fails.
  • When an IPv6 address is given for the Primary Hub, then the Robot is installed, however you cannot deploy or configure any probe on the Robot.
Solution:
Dual-stack mode does not work as the primary hub of the UIM environment is in the dual-stack IPv6 and the IP address that is used in the robot.cfg is dual-stack IPv4.
Dashboard Design Permission Requires Bus User Privileges
In the Account Admin, you can add the Dashboard Design permission to an ACL for an account contact user if the user wishes to create custom dashboards. However, the permission functions only for a bus user. Dashboard Design permission that is applied to an account contact user is ignored.
Exchange Monitor Setup Template Localization Issue
In CA UIM 9.0.2, the default profile name is not localized in the Exchange Monitor Setup MCS template.
Friendly Name with Special Characters Fails to Deploy the Schema
Symptom:
When you deploy a schema that has characters that are not valid in file names, the schema fails to deploy with the following error: Error occurred while creating/deploying schema probe package, Failed to deploy the probe package for the schema, <friendly_name> ScaleIO97db5264cdf49dbadf1de5928b0d9c98 :: <friendly_name>_schema.json."
Solution:
Define the friendly names with the characters that are valid in filenames.
Isilon Schema fails to Upload
Symptom:
Upload Isilon Schema fails with this error "There was a problem while importing. Please contact administrator." press OK to Continue
Solution:
This error typically occurs if the schema size is more than 1 MB. You can upload the Isilon schema with 1 MB as the maximum file size.
Interface Groups Not Supported with Mobile App
Currently, the application does not support interface groups with either Android or iOS devices.
Installation Fails on RHEL 7.4
Symptom:
UIM installation fails on RHEL 7.4 machines.
Solution:
If you are using RHEL 7.4, ensure that either the fonts local.conf file is configured or the dejavu-serif-fonts package is installed. For more information, see the RHEL Documentation.
Option 1
: The fonts local.conf file is configured. Create the /etc/fonts/local.conf file with the following contents:
<?xml version='1.0'?> <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> <fontconfig> <alias> <family>serif</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>sans-serif</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>monospace</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>dialog</family> <prefer><family>Utopia</family></prefer> </alias> <alias> <family>dialoginput</family> <prefer><family>Utopia</family></prefer> </alias> </fontconfig>
Option 2
: Run the yum install command to install the dejavu-serif-fonts package.
yum install dejavu-serif-fonts
Java-Based Probes Might Not Start on Secondary Robot Deployment
CA Unified Infrastructure Manager v8.51 and later are installed with Java 8. When upgrading to CA UIM v8.51 or later, if Java-based probes that are previously deployed to a robot use an older version of Java (for instance, Java 7), the probes might not start. To resolve this, redeploy java_jre version 1.7 to the robot and then restart the robot.
Java SDK Environment Variable Requirement
If you use the Java SDK to send messages to UIM, set the following environment variable to designate the loopback IP address for contacting the local robot. For example:
NIM_ROBOT_IP=127.0.0.1
JSON Schema Validation Fails
Symptom:Subsystems
Upload a JSON schema and the validation fails resulting in the following error:
[<schema_name>.json] is/are missing UIM metric definitions syntax.
Solution:
This error typically occurs when the UIM
metrics
definition section is missing from the JSON file or contains incorrect values in the
operator
and
severity
attributes.
To resolve the error, edit the schema file, and perform either of the actions:
  • In the
    metrics
    section of the schema, define only one value for the following attributes:
    operator
    and
    severity
    . These attributes do not support an array of values.
    Or
  • Remove the following attributes from the
    metrics
    section in the schema:
    thresholdenabled
    ;
    operator
    ;
    severity
    ;
    custom_message
    ;
    custom_clear_message
Manually Copy Security Certificates on the CABI External (Secondary Robot)
Before you deploy CABI External version and enable TLS v1.2 you need to manually copy the security certificates from the primary robot to the secondary robot.
When you are using Microsoft SQL Server as the database, you need to manually copy the trust store files (jks) from the primary robot to the secondary robot. The files are placed in the <Nimsoft>\security folder.
When you are using Oracle as the database, you need to manually copy the wallet files (SSO/PKCS12) from the primary robot to the secondary robot. The files are placed in the <Nimsoft>\security folder.
MCS Configuration Profiles Might Not Be Applied to All Members of Large Dynamic Groups
Dynamic groups are updated by default every 5 minutes. In large CA UIM environments, dynamic groups could have a thousand members or more. It is unlikely that Monitoring Configuration Service will be able to deploy or update configuration profiles to all members of a large dynamic group within the 5-minute interval. To resolve the issue, you can increase the configured interval. The interval is set with the group_maintenance_interval on nis_server. For details about modifying the group_maintenance_interval on nis_server, see the
Configure the Update Interval for Automatic Groups
section in the Create and Manage Groups article.
MCS MySQL, Oracle, or SQL Server Device-level Configuration Profile Overrides Might Not Be Marked with an Asterisk
Using Monitoring Configuration Service, you can create group-level MySQL, Oracle, or SQL Server configuration profiles. After MCS applies the group configuration profile to all members of a group, you can make device-level overrides. MCS marks each field with a device-level override on the device configuration profile with an asterisk. Under the following conditions, you might not see an asterisk on some of the device-level
alarm
fields that have overrides:
  • The group-level profile for a checkpoint was set to publish
    None
    or
    QoS
    , and then
  • The device-level override for the same checkpoint is set to
    Alarm
    or
    QoS and Alarms
mon_config_service Does Not Activate after Restart
Symptom:
When I restart the mon_config_service probe from Admin Console/ IM, the probe remains deactivated.
Solution:
If the mon_config_service probe remains deactivated after restarting, navigate to the Admin Console/ IM and select > Activate.
mon_config_service.log File Rotation Not Working Properly
Both log4j and NimLog are currently writing to the mon_config_service.log and this prevents the log file entries from rolling properly. To correct this issue, you need to modify the log4j.properties file and add an appropriate file size for the mon_config_service.log file. The workaround to correct this issue is:
  1. In Remote Desktop, open the log4j.properties file that is at <uim>\Nimsoft\probes\service\mon_config_service in a text editor.
  2. Remove FILE from the 'log4j.rootCategory=ERROR, FILE, CONSOLE' statement on the first line of the file.
    The statement becomes 'log4j.rootCategory=ERROR, CONSOLE'.
  3. Save the file.
  4. Specify an appropriate file size for the mon_config_service.log file. The default file size is 1024 KB.
    1. Access Admin Console.
    2. Select the hub on the
      Robots
      tab, and then select the
      Probes
      tab.
    3. Select the inline menu button for the mon_config_service.log file, and select
      Raw Configure
      .
    4. Select the
      Setup
      section.
    5. Select '
      +
      ' in the top right corner to create a key.
    6. Enter
      logsize
      in the Key field.
    7. In the Value field, enter an appropriate file size in kilobytes for the mon_config_service.log file.
    8. Select
      Create
      to add the log size key value.
    9. Select Update to save your changes.
Monitoring Configuration Service Profile Type Field Names
While MCS profile types and the associated probe configuration GUIs (either in Admin Console or Infrastructure Manager) for a particular probe will have the same configuration options, individual field names might not always match between them. For more information about the available fields for each probe GUI, see the documentation for each probe on the Probes site.
Monitors Not Deleting Even After Removing the Last Child Template (Override) for a Device
Symptom:
Create a group and add a device to this group. Also, ensure that no other override template is defined for the device. Then, override a template in this group and verify that the override template applies (monitors are published). Now, delete the override template. Even after deleting the override template, monitors created from the template for the device do not delete.
Solution:
When all the child template profiles that are associated with a device are removed, the device entry is deleted from the probe configuration file. The probe processes for all the devices that are found in the configuration file. Therefore, any device that was found earlier and now not present in the file is not processed. That is, monitors created earlier are not dropped.
In the current implementation, no way is available to manage the devices that are removed from the configuration file. As a workaround, restart the probe whenever this scenario occurs.
Name Resolution Conflicts on Debian Systems with the automated_deployment_engine Probe
By default Debian v6 uses the address 127.0.1.1 as the name resolution address. When a robot is deployed to a Debian 7 or 8 system using automated_deployment_engine, after system restart, the robot attempts to bind to 127.0.1.1 as the available address. Use the following work-around to avoid contention for 127.0.1.1 on your Debian system:
  • When installing the robot manually or with automated_deployment_engine, you must go to the target system after installation and must add the following line to the robot.cfg file:
robotip = ip_address
where
ip_address
is the desired IP address that the robot should bind to on the target system.
  • When deploying to Debian 6.0.5 using XML, you must define the
    <robotip>ip_address</robotip>
    option, where
    ip_address
    is the IP address that the robot should bind to on the target system.
Oracle Instant Client 12.2 Not Working
Symptom:
CA UIM 9.0.2 does not work with Oracle Instant Client 12.2.
Solution:
As a workaround, use Oracle Instant Client 12.1.
Probe Administration Returns an Unknown Error in a Windows Cluster Environment
When you attempt to configure a probe, probe administration might return an
unknown error
message in a Windows Cluster environment. Specifically, this problem has occurred with the ems probe, but can happen with other probes. To work around the issue, follow these steps:
  1.    Log in to Infrastructure Manager as the administrator.
  2.    On the Security tab, select
    Probe Administration
    .
  3.    Select
    New Probe
    to add an entry for the ems probe.
    1.        Select ems in the
      Probe
      drop-down list.
    2.        Select Admin in the
      Access
      drop-down list.
    3.        Enter an asterisk ( * ) in the
      IP Mask
      field, and select
      OK
      to save your changes.
Profile Reconciliation Function Removed From Monitoring Configuration Service
The Reconciliation function was moved from the mon_config_service probe to a new MCS Utilities Tools. The MCS Utilities Tool provides more flexibility to schedule reconciliation, more in-depth reports of detected differences, and increases the performance of the mon_config_service probe. To fix differences in configuration profiles that are managed by Monitoring Configuration Service, use the MCS Utilities Tool.
Probes Stop Working after Renaming the Robot Name and Restarting the Robot
Symptom:
The probes do not work after the robot name is changed and restarted.
Solution:
You must validate the probes after renaming the robot name. Validation can be done through the Infrastructure Manager interface.
Robot Installation Fails on UNIX
Symptom:
UNIX robot installation fails or the robot fails to start right after installation.
Solution:
Robot installations from Operator Console (OC) work as expected. However, this occurs with the silent installation using the Nimsoft Loader (nimldr) utility. If you see the following error message, then reattempt the installation a second time.
./niminit stop Failed to stop nimbus.service: Unit nimbus.service not loaded.
./niminit start Failed to start nimbus.service: Unit nimbus.service failed to load: No such file or directory.
If a robot fails to start, then stop and restart the robot.
Sub-Tenancy is Not Supported by CABI Availability Reports
Symptom:
CABI availability reports currently do not support the sub-tenancy feature. The data of all origins would be visible to the user on the CABI availability reports.
Solution:
There is no workaround available for this issue.
The nas AO (Auto Operator) Command Action Does Not Execute When There Is A Space in the Path (Support Cases 246133, 315782)
A command action cannot be parsed when the path contains spaces. Do not use spaces in the AO command path.
Unable to Migrate Existing Profiles to Enhanced Profiles After Upgrading from UIM 8.5.1 to UIM 9.0.2
Symptom:
After upgrading to UIM 9.0.2 from UIM 8.5.1, I do not see the enhanced profiles on Operator Console (OC) for my existing profiles, even after deploying the MCS package for enhanced profiles.
Solution:
You need to upgrade to the latest (non-enhanced) MCS template package before attempting to migrate the existing profiles to enhanced profiles. For detailed instructions, see
Migrating and Converting Existing profiles
in the Configuring Alarm Thresholds in MCS page.
Unable to Change "Need Client Authentication" in the data_engine UI
Symptom:
This issue occurs when TLS v1.2 is enabled for Oracle (UIM database) and you try to change the
Need Client Authentication
option. In the data_engine IM interface, when you try to change the
Need Client Authentication
option, the appropriate value for this option is not set in the sqlnet.ora file. The sqlnet.ora file is available in the
<
Nimsoft>\security
folder on the UIM Server computer.
Solution:
As a workaround, you must manually update the value of the SSL_CLIENT_AUTHENTICATION parameter. To do so, follow these steps:
  1. On the UIM Server computer, navigate to the
    <
    Nimsoft>\security
    folder.
  2. Locate and open the sqlnet.ora file.
  3. Update the SSL_CLIENT_AUTHENTICATION parameter in the sqlnet.ora file based on whether the
    Need Client Authentication
    option is selected or not (in the data_engine IM interface).
    For example, if the option is selected in the IM interface, the parameter must be set as follows:
    SSL_CLIENT_AUTHENTICATION = TRUE
    If the option is not selected, the parameter must be set as follows:
    SSL_CLIENT_AUTHENTICATION = FALSE
  4. Restart the data_engine probe.
Unable to Uninstall the Secondary Robot on an IPv6 Environment
Symptom:
On a pure IPv6 environment; if you try to remove the secondary robot from the hub, the
Ok
button is disabled after entering the IP address of the secondary robot.
Solution:
Detach the robot first from the hub and then uninstall it for successful removal of the secondary robot.
Unable to Create cdm Non-Enhanced Profile (Legacy)
Symptom:
When I try to create the cdm non-enhanced profile (legacy profile), I am unable to create it.
Solution:
The cdm non-enhanced (legacy) template requires cdm 6.30-MC to be present in the Local Archive. By default, cdm 6.30-MC is not present in the Local Archive. Therefore, if you want to create a cdm legacy template profile, ensure that cdm 6.30-MC is available in the Local Archive.
Unable to Open Probe Configuration Using Admin Console
Symptom:
The Configuration window does not open when you select the Configuration option for any probe in the Admin Console.
Solution:
This issue occurs when popups are blocked on your browser. Ensure that popup is not blocked for the Admin Console and select the Configuration option.
Upgrade Self-signed Certificates
The Java version was updated to Java 8. You must upgrade any self-signed certificates that are generated by CA UIM from previous CA UIM versions. If you do not upgrade the pre-existing certificates, HTTPS connections to CABI Server will not work due to the change in security encryption levels in Java 1.8. For more information, see Configure HTTPS in Admin Console or Operator Console (OC).
Using Variables for a Profile Name is Supported (Salesforce Case 418533)
The Monitoring Configuration Service now allows users to enter variable (for example, {device.ip} or {device.name}) for a Profile Name.
(For 9.0.2 or Later) Finding and Fixing Profile Differences using mon_config_service_cli
The following process to find and fix profile differences will not be applicable:
  1. Issue the Find-Profile-Diffs command to find robots with configuration profile differences.
  2. Issue the Fix-Profile-Diffs command to fix profile differences.
  3. Re-issue the Find-Profile-Diffs command with a file that lists the robots that had profile differences to verify that profile differences no longer exist.
Wasp does not extract the webapps
Symptom:
wasp does not extract the webapps and the entries like below are found in the wasp.log:
Feb 24 17:18:41:028 INFO  [Catalina-utility-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] No Spring WebApplicationInitializer types detected on classpath Feb 24 17:18:44:050 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during start Feb 24 17:18:44:051 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [[email protected]]     at java.util.concurrent.FutureTask.report(FutureTask.java:122)     at java.util.concurrent.FutureTask.get(FutureTask.java:192)     at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)     at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)     at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)     at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
Solution:
  1. Open registry
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NimbusWatcherService
    . In the key "ImagePath" change the value to path (same case) as it appears in Windows Explorer. (for.e.g. "C:\Program Files\Nimsoft\bin\nimbus.exe").
  2. Restart the "Nimsoft Robot Watcher" service.
Origin update in hub probe and override origin set by the hub in controller probe functionality is not working properly
When the Origin is updated on the hub or the controller, Origin name is not updating on alarms until we clear the alarms manually or restarting robot manually.
In the NAS, key is created including origin, which is then compared with existing key to update the database on which new entry or required fields are updated. If origin is updated, then for every incoming suppressed alarm, to avoid the issues in the alarm clear, new entry is created.
Edit and Delete Options Not Working Properly in the Reports Schedule Menu
Symptom:
When I try to schedule CABI reports in the OC UI, the Edit and Delete options are not working properly in the Schedule menu.
Solution:
The workaround is to use Schedules within CABI with the "overrides_custom.css" file applied as described in the KB Article.
[UIM 20.3.0] Device view columns are missing in Group and Inventory views of the Operator Console
In the new Operator Console, device view columns are missing at Group and Inventory views that are present in the UMP 20.1.
Group Device Columns: Alias, Caption, Description, OS Type, OS Version, OS Description, Origin, MAC Address, User Tag 1, User Tag 2, Removed, Bus Type.
Inventory Device Columns: Alias, Changed, Origin, Discovery Credentials.
[UIM 20.3.0] Interface group is not redirecting to device level in the Group view on the Operator Console
Interface group is not redirecting to device level at the Group view in the Operator Console. It is redirecting to group list view when clicking the interface group view.
[UIM 20.3.0] Select all checkbox in the Alarms table is not working properly
Symptom:
Select all checkbox in the Alarms table is not working properly in the Operator Console. All the alarms are not getting cleared and only alarms that are visible in the page are cleared using the Select all option. Also when the alarms are cleared, if you select the existing alarms again and the select all checkbox is not selecting any alarms.
Solution
: For the Select all feature to work properly, you must go to another page and come back to the alarm page.
[UIM 20.3.0] Generated PDFs for the Dashboards are not showing graphs for charts
In the Operator Console, generated PDFs for the dashboards are not showing graphs for charts. This issue happens for the existing dashboards.
[UIM 20.3.0] MCS Options: "Include Device Not in Group" and "Include Device Without Probe" are not working as expected
The "Include Device Not in Group" and "Include Device Without Probe" options are not returning all available devices with these conditions. In the Group profile settings of the MCS, when these settings are selected, the reference devices that are not in the group and the devices without the probes are not shown.
[UIM 20.3.0] Policy Id is displayed instead of Policy name in the Alarms view of the Operator Console
After creating an alarm policy in the Alarms view of the Operator Console, Policy Id is displayed instead of Policy name.
This issue has been fixed as part of the OC 20.3.2 patch release.
[UIM 20.3.0] Maintenance schedule for Nth day of a month is not working when the user timezone or target schedule timezone and the server timezone are different
In UIM 20.3.0, the maintenance schedule for the Nth day of a month not working, the schedule does not start on the scheduled date and time and remains inactive. This happens when the user time zone or target schedule time zone and the server time zone are different. If the scheduled date and the server date are different due to the time zone difference the maintenance schedule does not start on the scheduled date and time.
This issue has been fixed as part of the UIM 20.3.3 release.
[UIM 20.3.0] Wasp is not coming to online state when we upgrade from ump which has Self-cert deployed
In UIM 20.3.0, while upgrading from UMP to OC, wasp does not come to online state if the existing UMP has Self-cert deployed.
This issue is applicable only if you are upgrading from a version prior to UIM 20.3.0.
[UIM 20.3.0] In the alarms page, for the alarms that are created as a result of an alarm policy, the link to the policy is not enabled for newly created alarm policies
When the alarms are created as a result of an alarm policy in the alarms page of the Operator Console, the link to the alarm policy is not enabled for newly created alarm policies. After the restart of wasp, the policies are enabled with the links. New alarms that are created as a result of the new alarm policies after the restart  will have the same issue.
This issue has been fixed as part of the OC 20.3.2 patch release.
[UIM 20.3.0]  No QOS metric for profile 'AD Server Services' in the Ad_server MCS template
In UIM 20.3.0, there is no QOS metric for profile 'AD Server Services' in the Ad_server MCS templates.
[UIM 20.3.0] Change Password for Account Users who are added manually in Account Admin is not available
In UIM 20.3.0, for any new users who are added manually in Account Admin, change password option is not available. Users cannot change the password using the Operator Console.
This issue has been fixed in the UIM 20.3.3 release.
[UIM 20.3.0] Alarm Policy search filters does not give accurate results
In UIM 20.3.0, the alarm policy search filters results give inaccurate results. The search results are shown for the partial search string when there are more than two letters in the search. The search results also take long to provide the alarm policies in the results.
[UIM 20.3.0] Operator Console does not timeout
In UIM 20.3.0, Operator Console does not timeout and the session remains active even after the session is idle for 72 hours.
This issue has been fixed as part of the OC 20.3.2 patch release.
Additional Known Issues
  • For the new known issues in the UIM 20.3.1 release, see the Known Issues section in the UIM 20.3.1 article.
  • For the new known issues in the OC 20.3.2 release, see the Known Issues section in the OC 20.3.2 Patch article.
  • For the new known issues in the UIM 20.3.3 release, see the Known Issues section in the UIM 20.3.3 article.