Devices getting discovered again after doing deep clean
Article ID: 383747
Updated On:
Products
Issue/Introduction
We are seeing issues with the deep clean process. Recently, two devices were deleted using the deep clean process.
And the devices got discovered again in the Inventory, showing the monitoring host with the hub and inactive robot remains in the admin console. We are seeing a time delay in the process of deleting a device.
Environment
- DX UIM 23.4 CU2
Resolution
Delete devices and while deleting, enable 'Prevent Rediscovery' Checkbox, so that in the future it will not rediscover them.
Did you select/enable 'Prevent rediscovery?'
'Prevent rediscovery' is NOT selected by default.
In the OC wasp.log, when you click on delete devices and choose that option you can watch the activity:
Dec 09 16:04:43:406 DEBUG [http-nio-8081-exec-4, com.firehunter.ump.auth.OCAuth] User prin com.nimsoft.nimbus.probe.service.wasp.auth.NimbusUserPrincipal@47aa02e(administrator) found for administrator
Dec 09 16:04:43:485 DEBUG [http-nio-8081-exec-4, com.firehunter.ump.auth.OCAuth] User prin com.nimsoft.nimbus.probe.service.wasp.auth.NimbusUserPrincipal@47aa02e(administrator) found for administrator
Dec 09 16:04:43:656 DEBUG [ForkJoinPool.commonPool-worker-3, com.nimsoft.discovery.common.nimbus.NonPooledNimRequestWrapper] Sending remove_master_devices_by_cs_ids request to /DX_UIM_domain_example/Primary-hub-example/primary-hub-robot/discovery_server
Dec 09 16:04:44:141 DEBUG [Catalina-utility-2, com.nimsoft.nimbus.probe.service.wasp.WaspLifecycleListener] Memory Status: Max Limit: 3641MB, Allocated: 3252MB, Free: 1212MB, Used: 2040MB
Dec 09 16:04:44:141 DEBUG [ForkJoinPool.commonPool-worker-3, com.nimsoft.discovery.common.nimbus.NonPooledNimRequestWrapper] Sending close_alarms_for_device_list request to /DX_UIM_domain_example/Primary-hub-example/primary-hub-robot/ems
Dec 09 16:04:53:422 DEBUG [pool-35-thread-1, com.nimsoft.discovery.common.nimbus.NonPooledNimRequestWrapper] Sending probe_config_get request to /DX_UIM_domain_example/sample-demohub1/sample-win-robo/controller
Dec 09 16:04:53:672 DEBUG [pool-35-thread-1, com.nimsoft.discovery.common.nimbus.NonPooledNimRequestWrapper] Sending _nis_cache_clean_custom request to /DX_UIM_domain_example/sample-demohub1/sample-demohub1/controller
Dec 09 16:04:53:922 DEBUG [pool-35-thread-1, com.nimsoft.discovery.common.nimbus.NonPooledNimRequestWrapper] Sending get_info request to /DX_UIM_domain_example/sample-demohub1/sample-win-robo/controller
Dec 09 16:04:54:156 DEBUG [Catalina-utility-3, com.nimsoft.nimbus.probe.service.wasp.WaspLifecycleListener] Memory Status: Max Limit: 3641MB, Allocated: 3252MB, Free: 1205MB, Used: 2047MB
Dec 09 16:04:54:172 DEBUG [pool-35-thread-1, com.nimsoft.discovery.common.nimbus.NonPooledNimRequestWrapper] Sending _uninstall_robot request to /DX_UIM_domain_example/sample-demohub1/sample-win-robo/controller
The tables listed below will display the current state of the device/robot, e.g.,
select * from CM_BLACKLIST_DEVICE order by dev_name ASC
select * from CM_BLACKLIST_COMPUTER_SYSTEM
In testing, it didn't work as expected IF the device was already/previously processed with 'Prevent rediscovery' enabled.
So, to test further, cleared those BLACKLIST tables of the specific entries using a DELETE statement.
Then rediscovered the device and checked to make sure it was in the Inventory and it was there.
Then went back into the OC Inventory and ran the Delete devices with the 'Prevent rediscovery' button enabled.
The wasp.log entries remained the same as I showed below, but you can check the blacklist tables and see that the device was successfully blacklisted and the 'time_added' has been updated.
This is 'working as designed' and as expected.
In the discovery_server log you can also see the fact that the device was excluded from discovery:
Dec 09 16:42:48:139 [hubWorker-1] TRACE com.nimsoft.nis.infrastructure.RobotInfo - robot addr=/DX_UIM_domain_example/sample-demohub1/sample-win-robo ip=10.###.###.### lastInstChangeTime=1730817194000
Dec 09 16:42:48:349 [ConsumerTask] INFO com.nimsoft.discovery.server.ec.importer.CtdIPDeviceImporter - device import begin: numIpDevices=1
Dec 09 16:42:48:351 [ConsumerTask] TRACE com.nimsoft.discovery.server.ec.importer.CtdIPDeviceImporter - Beginning import of device: {"ctdType":"ComputerSystem","OperationalState":"Up","Origin":"sample-demohub1","PrimaryDnsName":null,"PrimaryIPV4Address":"10.###.###.###","PrimaryIPV6Address":null,"PrimaryMacAddress":null,"PrimaryOSType":"Windows-10","PrimaryOSVersion":null,"PrimaryRole":"Host","ProcessorType":null,"Roles":"Host","ctdEntityTypeFQName":"Entity.Element.Device.IPDevice.ComputerSystem","customProperties":{"CorrelationId":"D6763D19186816835E8A1260D920D635C","CorrelationNames":"sample-win-robo","DeviceId":"D6763D19186816835E8A1260D920D635C","EnrichedOrigins":null,"NimbusType":"Robot","OSDescription":"Service Pack 0 Build 19045","ProbeName":"controller","RobotDeviceId":"D6763D19186816835E8A1260D920D635C","RobotInstanceId":"D6763D19186816835E8A1260D920D635C","RobotName":"sample-win-robo","cs_id":0,"cs_key":null,"ctdId":"D6763D19186816835E8A1260D920D635C:D6763D19186816835E8A1260D920D635C"},"descript
on":null,"id":"D6763D19186816835E8A1260D920D635C:D6763D19186816835E8A1260D920D635C","label":"sample-win-robo","typeName":"ComputerSystem"}
Dec 09 16:42:48:352 [ConsumerTask] DEBUG com.nimsoft.discovery.server.ec.importer.NisElementAcceptor - Skipping excluded DeviceId: D6763D19186816835E8A1260D920D635C
Dec 09 16:42:48:353 [ConsumerTask] TRACE com.nimsoft.discovery.server.ec.importer.CtdIPDeviceImporter - Device import for D6763D19186816835E8A1260D920D635C:D6763D19186816835E8A1260D920D635C took 2 milliseconds.
Dec 09 16:42:48:353 [ConsumerTask] INFO com.nimsoft.discovery.server.ec.importer.CtdIPDeviceImporter - device import end: elapsed milliseconds = 3
Feedback
