Resolved Issues

uim902
The following are the resolved issues in 20.1.0.
2
2
ada_inventory
  • (1.42 HF2) Fixed an issue where the ADA console is not being able to register with the UIM if we delete and add the new/same console to the UIM. (Support Case: 1356178)
attr_publisher
  • (9.20 HF8) Fixed an issue where users were receiving the Application Error Event 1000 error. To resolve the issue, the size of the buffer value_to_niscache and value_to_niscache_map increased to 4k from 512. (Support Case: 20077272)
CABI for UIM
  • Fixed an issue where Login failed after CABI Installation. (Support Case: 20051609)
  • Fixed an issue where out of the box report on devices showing incorrect data in CABI Jasper report. (Support Case: 20103433)
  • Fixed an issue where UIM Availability Reports show wrong groups. (Support Case: 20003645)
controller
  • (7.97 HF6) Fixed an issue in which 7.97 hub was dropping the tunnels and was not allowing the creation of new ones. Hub assigns the port to the tunnel connection by asking the controller. The controller is always assigning the new port and not using previously released ports, which was causing delay in searching for the available port. Optimized it to reuse the previous released ports. (Support Case: 01307453)
  • (7.97 HF7 and 9.20 HF7) Fixed an issue where the secondary hub stopped sending QoS from all probes after the upgrade to 9.20. Added the extra parameter as "restmon_qos" in the RESTMon QoS message and handled the same at the plugin_metric level to identify the RESTMon QoS message to solve this issue. (Support Case: 20058295, 20040794, and 20033089)
  • (7.97 HF8 and 9.20 HF9) Fixed an issue causing the crashes due to the BM UIM ACL handling RCE and Probe DoS vulnerabilities. Added fix for the unauthenticated remote code execution vulnerability in Nimsoft nimbuscontroller. (Support Case: 20093616, 20101721)
  • (9.10 HF1) Fixed an issue where alarms were not getting generated as per CI selected in the alarm policy. Alarms were not getting generated as per the ci_name selected in the alarm policy because plugin_metric always used to get the probe ci_name from niscache. However, the  docker_monitor probe sends ci_name as a part of qos_message. To fix the issue, a functionality in plugin_metric has been added that allows to get the ci_name from qos message if it is not found in the niscache folder. (Support Case: 20051916)
  • (9.20 HF2) Fixed the robot failover issue. Check has been put to accept requests from the primary hub if the robot has been switched to the secondary hub when the proxy mode is enabled in the controller. (Support Case: 20051408)
  • (9.20 HF3) Fixed two issues as part of this hotfix. Fixed the robot failover issue. Also, fixed an issue where the alarm policy alarms did not contain the robot's user tag. (Support cases: 20051408 and 20063366)
  • 9.20S HF3) Fixed an issue where the alarm policy alarms did not contain the robot's user tag. (Support Case: 20063366)
  • (9.20 HF5) and 9.20S HF5) Fixed an issue where multiple instances of robot were running, which was exhausting the CPU resources. (Support Case: 20084151)
  • (9.20S HF4) Fixed an issue where robots were not failing-over in a mixed secure robot environment. The issue is coming as hub sends check-in request to all its robots after coming up. In a secure environment, non-secure robots send robot-up request on 480002 port and hub_adapter runs on 48002 port. hub_adapter is not included in the core component, so it starts after some time. And, before it starts, robot-up request comes and fails. Changes have been made so that hub_adapter process starts right after hub. This allows it to handle all the requests from non-secure robots. (Support Case: 20069927)
  • (9.20S HF7) Fixed the following issues: (Support Cases: 20097684, 20089674, 20093286, 20075343, 20074324, 20058295, 20040794, and 20033089)
    • Controller had special handling for SID expire on robots. Proxy cannot differentiate between the controller and probe, so was giving controller SID to probe upon expire. This was causing permission denied. Fix has been provided to make controller get the SID on its own when the SID expires.
    • Fixed an issue where the secondary hub stopped sending QoS from all probes after the upgrade to 9.20. Added the extra parameter as "restmon_qos" in the RESTMon QoS message and handled the same at the plugin_metric level to identify the RESTMon QoS message to solve this issue.
  • (9.20 HF10)  Fixed an issue where Alarms from cdm probe not being cleared in the cdm MCS Enhanced Profile. This was because the alarms are not being cleared when there are more than one alarm condition. Added fix to clear alarm for all the conditions. (Support Case: 20141321)
  • Fixed an issue where CPUs maxed out when robot runs twice. (Support Case: 20084151)
  • Fixed an issue where passive robot (controller) generates illegal SID error. (Support Case: 20100511)
  • Fixed an issue with the Application Error Event with the code 1000 on the robots. (Support Case: 20077272)
  • Fixed a Robot failover issue in UIM 9.1.0. (Support Case: 20051408)
  • Fixed an issue where Robots are not failing over in a mixed secure robot 9.2hf3 environment. (Support Case: 20069927)
Dashboard
  • Fixed an issue where Dashboard seems not to execute all queries if invoked via drill down. (Support Case: 1341223)
  • Fixed an issue where UMP dashboards using database queries stop working after a while. (Support Case: 1294205)
Dashboard Portlet
  • Fixed an issue with the Dashboard which is not able to load dashboard definition . (Support Case: 20093887)
  • Fixed an issue with the Wasp dashboard crash after UIM 9.10 update. (Support Case: 20007511, 20005479)
data_engine
  • (9.20 HF1) Fixed an issue in which after upgrading from 9.0.2 to 9.2, the data_engine probe 9.20 did not empty the hub queue due to initialization issues. (Support Cases: 20051358 and 20050695)
  • (9.20 HF2) Fixed an issue in which users were receiving the "You have exceeded your Qos License" error. (Support Cases: 20057740, 20051358, and 20050695)
  • (9.20 HF3) Fixed an issue in which data_engine was not adding the new metric definitions to the database. The issue was occurring because of the nan (not a number) value that was getting passed to the database. The database was then throwing exception and resetting the connection. This hotfix has resolved this issue by discarding nan before sending it to the database. (Support Cases: 20085489 and 20066349)
  • (9.20 HF4) Fixed an issue in which users were facing issue with the qos_processor queue when upgrading from 8.51 to 9.02. During an upgrade, data_engine runs a script that changes the checksum and uses SHA1 encoding to evaluate the checksum. Whereas,  qos_processor and data_engine are still evaluating the checksum based on SHA0, which causes the checksum mismatch and hence the issue. The hotfix resolves the issue by changing hashing in data_engine and qos_processor to use SHA1. (Support Cases: 20028603, 20089089, 20010894, and 20083614)
  • Fixed an issue related to data_engine probe which doesn’t start after upgraded to 9.20. (Support Case: 20051358)
  • Fixed an issues where data_engine is not adding new metric definitions to the database. (Support Case: 20085489)
  • Fixed an issue related to data_engine looping in initialization and the Hub queue is growing. (Support Case: 20050695)
  • Fixed an issue where GRE  QOS License exceeds license by 79897 objects. (Support Case: 20056526)
  • Fixed an issue where QOS is not showing for any device. (Support Case: 1369585)
  • Fixed an issue with the data_engine which is throwing multiple errors in the log and missing data in DB. (Support Case: 20066349)
discovery_server
  • (9.0.3 HF3) Fixed an issue where the vCenter is being correlated with the host instead of being decorrelated. To fix the issue, modified the nisMetaData index to include the virtual ID. (Support Case: 20031152)
  • (920 HF1) Fixed an issue in which discovery_server was not picking up changes in user tags. This issue was occurring in a scenario where robot was going down when the tag was getting changed in the controller configuration and only the robot status was getting updated. To fix the issue, changed the mechanism to update the attributes. (Support Case: 20105364)
  • Fixed an issue in which Device xmi b104vpn01 does not show interface metrics from Interfaces tab. (Support Case: 20052255)
  • Fixed an issue of duplicate entry for the Discovery_server of same origin with different case. (Support Case: 20047981)
  • Fixed an issue where vCenter is being correlated with the host instead of being decorrelated. (Support Case: 20031152)
  • Fixed an issue with the discovery_server which is not picking up changes in user tags. (Support Case: 20105364)
  • Fixed an issue where discovery_server keeps logging exceptions. (Support Case: 20033061)
distsrv
  • (9.20 HF8) Fixed an issue in which users were unable to distribute to more than one client at a time using 9.20 Secure bus. The reason is that distsrv tries to identify whether the distribution is happening on the same host or on a different host based on the IP. With secure bus, the nametoip returns loopback (127.0.0.1). So, distsrv considers that the distribution is happening on the same machine and puts it into the queued state. To resolve the issue, an extra check has been added in case of the secure bus to compare the robot addresses as well. (Support Case: 20132625)
  • Fixed an issue with more than one client at a time not being distributed using 9.20 Secure. (Support Case: 20132625)
fault_correlation_engine
  • (1.68 HF2) Fixed an issue where the Fault correlation engine is unable to set node state. (Support Case: 01365086)
hub
  • (7.97 HF6) Fixed the following issues:
    • Fixed an issue in which the UIM primary hub was becoming unavailable. This issue was occurring because the CPU usage was higher due to continuous while loop. To resolve the issue, added sleep to avoid CPU consumption. (Support Case: 20032589)
    • Fixed an issue where the bulk size for a get queue was intermittently getting changed from configured amount to "blank". To fix the issue, on queue connection reset, used the configuration value for the queue bulk size. (Support Case: 01312205)
  • (9.10 HF4, 9.10S HF4, 9.20 HF6, and 9.20S HF6) Fixed an issue in which users were unable to log into IM and probe logins were also failing. The login information in UIM uses encryption mechanism that includes current date and time. In those scenarios where the encryption was producing a login string starting with NULL character '\0', the decryption was failing and the hub login was unsuccessful. This hotfix has resolved the issue. (Support Case: 20092472)
  • Fixed an issue where Perl nimalarm is blocked/suppressed by hub. (Support Case: 20083641)
  • Fixed an issue where the primary and secondary hubs connected via tunnels can no longer connect after SP1 - NOT SECURE update. (Support Case: 1353985)
  • Fixed an issue where UIM Primary Hub becomes unavailable. (Support Case: 20032589)
  • Fixed an issue with the hub not being able to import more than 100 groups. (Support Case: 20040934)
  • Fixed an issue with the hub which adjusts the  bulk size for a get queue from configured amount to blank. (Support Case: 1312205)
  • Fixed an issue with the LDAP groups which are not visible in admin console portlet. (Support Case: 20018982)
  • Fixed an issue with the tunnel server where it goes down when handshake failures occur repeatedly. (Support Case: 835880)
  • Fixed an issue with UIM going completely down. (Support Case: 20092773, 20092560)
  • Fixed an issue with the Passive Robots being showed up duplicate after restart of the HUB. (Support Case: 20067381)
  • A new configuration parameter epoll_wait_timeout has been introduced through which the user can set a different timeout. If the parameter is not specifically configured in hub.cfg then default value of 15 secs will be set. For Hub to Hub tunnel communication, this parameter needs to be configured in tunnel server hub (applicable for both Secure and Non-secure hubs) under Tunnel/server section of hub cfg. Valid values for this parameter are between 100 and 15000 (100 ms to 15 secs). (Support Case: 01353985)
Java SDK
  • Fixed an issue related to the hub permissions. (Support Case: 20061094)
Liferay
  • Fixed an issue with the Liferay where update portal settings not working. (Support Case: 20102555)
  • Fixed an issue with the UMP Portal Settings in which clicking the Save button doesn’t give any action. (Support Case: 01367900, 20006662)
  • Fixed an issue with X-frame error attemping to integrate USM frames into a service portal page, getting error. (Support Case: 20029732)
  • Fixed an issue related to the Import Image to Private nor Update Company Logo.  (Support Case: 20083986)
maintenance_mode
  • (9.02 HF4) Fixed an issue where spectrumgtw syncing of the maintenance schedules was causing sluggish UMP performance. (Support Case: 20042333)
  • (9.10 HF1 and 9.20 HF1) Fixed an issue in which users were getting duplicate maintenance schedules after Spectrum integration. (Support Case: 20045094)
  • Fixed an issue related to the unknown error when deleting robot from maintenance schedule. (Support Case: 20047617)
  • Fixed an issue with spectrumgtw syncing of maintenance schedules causing sluggish ump performance. (Support Case: 20042333)
  • Fixed an issue with the UMP Maintenance Schedules at wrong day/time. (Support Case: 1278720)
  • Fixed an issue with USM which throws an error when removing device from maintenance schedule. (Support Case: 20109406)
  • Fixed an issue where UIM is impacting Spectrum causing memory issues with model creations/deletions. (Support Case: 20046860)
  • A new background task is added which handles the maintenance schedules by adjusting the time. It is scheduled to run on startup and every 24 hrs by default, the time interval is configurable. To change the time interval, "handle_dst_interval" key should be set under the setup section. As an example, In order to schedule the task to run every 24 hrs, set as: "handle_dst_interval=24" (Support Case: 20280779,20094790,20098531)
mon_config_service
  • (9.10 HF2 and 9.20 HF1) Fixed an issue in which MCS could not handle unreachable robots on delete. This hotfix contains the fix for the excessive growth of the SSRV2AudittrailModification tables. This hotfix turns off the entries into the SSRV2AudittrailModification tables whenever the profile is modified. (Support Case: 20032772)
  • (9.10 HF3 and 9.20 HF1) Fixed an issue where the LDAP account user was unable to select the host location for the remote MCS profiles. (Support Case: 20069408)
  • (9.10 HF3 and 9.20 HF1) Fixed an issue in which the last deployed date of an MCS profile in USM was always getting the current time. This hotfix contains the fix for displaying the last deployed date correctly in the UMP UI.
  • (9.20 HF2) Fixes the following issue: (Support Case: 20084368)
    • Fixed an issue where the new name of a USM group was not reflected in the Alarm Policy UI.
    • Fixed an issue where the net_connect auto policies were getting deployed to the target robot instead of the poller robot.
    • Deployment of profiles are decoupled from processing of devices at the group level for increasing the performance of MCS.
  • Fixed an issue where "Last deployed date" of an MCS profile in USM is always current time and not the time it was actually deployed.. (Support Case: 20069054)
nas
  • Fixed an issue where NAS Name Services is replacing hostnames with IP addresses. (Support Case: 20106226)
  • Fixed an issue with Alarm Enrichment and/or NAS not working properly. (Support Case: 20103051)
ntevl
  •   (4.32 HF6) Fixed an issue where ntvel probe fails to start when user configured language_strings. Added a required function declaration to solve the crash issue of the post VS2017 migration. (Support Case: 20100795)
nisapi_wasp
  • (9.03 HF1) Fixed an issue where users were not able to create an alarm policy for large dynamic groups. (Support Case: 20076947)
oracle
  •   (5.41 HF3) Fixed performance issues with the oracle probe where the probe stops working with few password combinations. (Support Case: 20060315)
policy_management_ws
  •   (0.2.2 HF1) Fixed an issue where the alarm UNITS are displayed in the wrong way. This hotfix addresses the issue of interchanging alarm units in plugin_metric.cfg when TOT is selected while creating the alarm policy in UI. (Support Case: 20022178)
  • (0.2.2 HF2) Fixed an issue with the multiple UMP nodes where the second UMP wasp log has errors for subscription to queue policy_management.(Support Case: 20001936)
  • (0.2.2 HF3) Fixed an issue where the new name of the USM group is not reflected in Alarm Policy UI. The issue was occurring in the Operator UI console where alarm tables still show the older group name in the “Applies To” column after renaming the group name. To fix the issue, Net_connect auto policies are deployed to the target robot instead of the poller robot. (Support Case: 20084368)
Performance Reports Designer
  • Fixed an issue where Scheduled PRD reports are blank. (Support Case: 20149155)
  • Fixed an issue where Performance Report Hostname Display with Hub Name. (Support Case: 20088724)
  • Fixed an issue related to the Duplicated Devices in S_QOS_DATA table. (Support Case: 20078740)
qos_processor
  • (9.10 HF1) Fixed an issue in which users were facing issue with the qos_processor queue when upgrading from 8.51 to 9.02. During an upgrade, data_engine runs a script that changes the checksum and uses SHA1 encoding to evaluate the checksum. Whereas,  qos_processor and data_engine are still evaluating the checksum based on SHA0, which causes the checksum mismatch and hence the issue. The hotfix resolves the issue by changing hashing in data_engine and qos_processor to use SHA1. (Support Cases: 20028603, 20089089, 20010894, and 20083614)
Report Scheduler
  • Fixed an issue where Report Scheduler considers the / character to be invalid in an email address. (Support Case: 20007924)
  • Fixed an issue where ReportScheduler does not print legend in table format. (Support Case: 1316254)
  • Fixed an issue where scheduled PRD's are empty. (Support Case: 20095536)
  • Fixed an issue where Scheduled reports contain empty graphs. (Support Case: 20003239, 20031928)
  • Fixed an issue where the existing PRD reports are unable to modify these reports after the upgrade. (Support Case: 20057158)
  • Fixed an issue where USM Report Scheduler jobs fail with errors. (Support Case: 20087846)
sla_engine
  • (9.10 HF1) Fixed an issue in which data_engine 9.20HF2 was breaking sla_engine. (Support Case: 20068655 and 20070361)
  • (9.10 HF2) Fixed an issue where SLA Calculation was resulting in 0% fulfillment if excluded period was set. (Support Case: 20115483)
    sla_engine gets the licenses from data_engine and checks the number of licenses. With the new licensing model, data_engine does not provide a license. With this fix, sla_engine has been modified and it no longer gets the license.
snmpcollector
  • (4.0.3 HF1) Fixed an issue where users were unable to create a profile for an snmpv3 device on the snmpcollector, either directly or through callbacks. (Support Case: 20096400)
Spooler
  • Fixed an issue where Alarm Policy alarms do not contain the robot's user tags. (Support Case: 20063366)
  • Fixed an issue with the Perl SDK where nimalarm doesn’t work with the hub version later than 7.80. (Support Case: 1361195)
  • Fixed an issue with the Perl SDK where Probe callback failed and the arguments return NULL values. (Support Case: 20036624)
  • Fixed an issue with the Secondary Hub which stops to send QOS from ALL probes after Upgrade to 9.20. (Support Case: 20058295)
  • Fixed an issue with xendesktop metrics which do not return any metrics. (Support Case: 20040794, 20033089)
  • Fixed the memory leak issues post hub/robot hotfixes. (Support Case: 20111208, 20219379)
uimapi
  • (9.10_HF1) Fixed an issue where users were getting problems with uimapi as timeout for maintenance was not implemented in uimapi. This hotfix resolves the issue. (Support Case: 20192186)
  • Fixed an issue when attempting to use uimapi which throws Internal Server Error of error code 500. (Support Case: 20103280)
  • Fixed an issue where uimapi failing on error 500 for some hubs. (Support Case: 1327983)
webservices_rest
  • (9.20 HF1) Fixed an issue in which the logmon directory list callback was returning empty response through the webservices_rest API. (Support Case: 20026882)
  • Fixed an issue where WebServices Rest probe 9.20 throws Internal Server Error. (Support Case: 20053846)
UMP
  • (ump_dashboard_852_HF7) Fixed an issue in which the data was not visible in the dashboard and UMP dashboard charts, tables were showing 'no data to display'. (Support Case: 01309265 and 01260385)
  • (ump_usm_852_HF25) Improved the performance in the USM monitoring tab. (Support Case: 1298008)
  • (ump_listdesigner_904_HF1 and ump_listviewer_904_HF1) Fixed an issue where the ListViewer and ListDesigner views were not responding when trying to open the saved views. (Support Case: 20031642)
  • (ump_root_902_HF1) Fixed an issue in which when a portlet was added, the entire page was getting filled. Users had to refresh the page to resolve the issue. Now, with this hotfix, no manual step is required and the view is displaying correctly. (Support Case: 01247936)
  • (ump_usm_904_HF4) Fixed an issue in which junk characters were appearing on the UMP screen. (Support Case: 1336779)
  • (ump_usm_910_HF2) Provides updates for MCS by deploying corrections to the existing UMP portal.
  • (ump_usm_910_HF3) Fixed an issue in which MCS could not handle unreachable robots on delete. This hotfix contains the fix for the excessive growth of the SSRV2AudittrailModification tables. This hotfix turns off the entries into the SSRV2AudittrailModification tables whenever the profile is modified. (Support Case: 20032772)
  • (ump_usm_910_HF4) This hotfix contains the fix for displaying the last deployed date correctly in the UMP UI. This hotfix also contains the fix that selects the host location of the LDAP account user for remote profiles. For example, Network Connectivity (Enhanced). (Support Cases: 20069054 and 20069408)
  • (ump_usm_920_HF2) Fixed the following issues:
    • Fixed an issue where the new name of a USM group was not reflecting in the alarm policy UI. (Support Case: 20084368)
    • Fixed an issue where the net_connect auto policies were getting deployed to the target robot instead of the poller robot. (Support Case:
    • Fixed an issue where the deployment of the profiles were getting decoupled from the processing of the devices at the group level for increasing the performance of MCS.
  • (ump_reportscheduler_920_HF1) Fixed an issue where users were unable to modify existing PRD reports. (Support Case:20057158)
  • (ump_usm-920_HF3) Removed the default maximum 100 device count limit for the static group creation.
    • (ump_reportscheduler_920_HF2) Fixed an issue where scheduled reports were not showing any data. (Support Case: 20105007)
  • (ump_reportscheduler_920_HF3) Fixed an issue where account/origin-based filtering was not working for scheduled reports. (Support Case: 20149155)
  • (ump_usm_920_HF1) This hotfix resolves the following issues:
    • Contains the fix for displaying the last deployed date correctly in the UMP UI. (Support Case: 20069054)
    • Contains the fix for selecting the host location of the LDAP account user for remote profiles. For example, Network Connectivity (Enhanced). (Support Case: 20069408)
    • Contains the fix for the excessive growth of the SSRV2AudittrailModification tables. Now, this fix turns off entries into the SSRV2AudittrailModification tables whenever the profile is modified. (Support Case: 20032772)
  • Fixed an issue where MCS View of Monitoring Profile is very slow. (Support Case: 1184464)
  • Fixed an issue where Report Scheduler considers the / character to be invalid in an email address. (Support Case: 20042186)
  • Fixed an issue where the metrics on USM details page seems grayed out. (Support Case: 20054578)
  • Fixed an issue where UMP displays no alarms at Details tab. (Support Case: 1347792)
  • Fixed an issue which removes or stops user access to UMP USM state field. (Support Case: 20040127)
  • Fixed an issue with the CDM Disk free metrics which are showing incorrect (6000+%). (Support Case: 20054580)
  • Fixed an issue with the Group_info option being enabled by default in 9.20. (Support Case: 20051451)
  • Fixed an issue with the USM Group Editor where static group filter shows limited results. (Support Case: 20118128)
  • Fixed an issue with UMP Performance. (Support Case: 1258194)
  • Fixed issues related to the USM screen corruption and removal or stop of usm state field. (Support Case: 20066968)
  • Fixed monitoring tab access issues on few particular servers. (Support Case: 1355194)
  • Fixed the USM screen corruption issue after upgrade to 9.02. (Support Case: 1372812 )
  • Fixed some UMP issues after 9.0.2 upgrade. (Support Case: 1364799)
url_response
  • (4.0.3 HF1) Fixed an issue with the URL Check (Enhanced) template where alarms are not being raised when url is down. The template has been fixed to add “active = yes” key in the alarm. (Support Case: 20072090)
wasp
  • Fixed an issue where [PDS] Dashboard navigator does not work. (Support Case: 1341208)
  • Fixed an issue where UMP keeps hanging. (Support Case: 20016546)
  • Fixed an issue where USM intermittently hanging after upgrade from 8.5.1 => 9.0.2 => 9.1.0. (Support Case: 20014504)
  • Fixed an issue where Wasp probe takes a lot of time to start. (Support Case: 20009723)
  • Fixed an issue where Windows NimBus Robot is unable to download after UIM9.0.2 upgrade. (Support Case: 20031255)
  • Fixed the UIM VULNERABILITIES issues. (Support Case: 20050989)
  • Fixed the UMP Server vulnerabilities issues. (Support Case: 1367897)
  • Fixed the Vulnerabilities on CA Unified Infrastructure. (Support Case: 20026423)
  • Fixed an issue with the Error messages on WASP log - Startup. (Support Case: 20004176)
xendesktop
  • (4.2.4 HF1) Fixed an issue in which Xendesktop probe and Nimbus Robot Service are sending passwords over the network in Clear Text. (Support Case: 20068319)
xtremIO
  • (1.01 HF5) Fixed an issue in which one of the profile in the xtremio probe is in error state. This hotfix updated all the REST calls to support multi cluster scenario. (Support Case: 20102386)