UIM 20.3 / 20.3.1 - CABI v4.30 failing to install on Windows
search cancel

UIM 20.3 / 20.3.1 - CABI v4.30 failing to install on Windows


Article ID: 204096


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


This article provides a workaround if the cabi bundled probe version 4.30 is failing to install on Windows in UIM 20.3 or 20.3.1. 


UIM 20.3.1 
cabi bundled v4.30


1. Perform a FULL clean up of the current CABI installation which is failed: 

a). Deactivate both the cabi probe and cabi wasp probe. 

b). Delete the cabi wasp probe and then delete the cabi wasp probe directory 
- found here: \Nimsoft\probes\service\wasp. 

c). Go to the cabi probe directory and create a copy of the js-pro-drop.ddl file found here:
- found here: \Nimsoft\probes\service\cabi\config\scripts\drop_tables\1.2\sqlserver (assuming an sql server db).
Notes: This will be used shortly to drop all of the JI (CABI jasper report server) tables. 

d). Delete the cabi probe and delete the cabi probe directory. 
- found here: \Nimsoft\probes\service\cabi

e). Delete the c directory located on the cabi robot. 
- found here: \Nimsoft\c

f). Go to the UIM Database (SQL Management Studio) and run the drop script against the UIM database. 
- js-pro-drop.ddl file copied earlier.
Notes: This file can be opened via notepad and copied over. 

2. Ensure the robot.cfg has been configured on the cabi robot. This enabled communication to the UIM database which is required for both cabi and wasp probes. 

Configure robot.cfg - https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/configure-robot-cfg.html

3. Perform a new installation (We will use the cabi bundled 4.20 instead of 4.30). 

a). Drag and drop the cabi bundled probe version 4.20 to the robot in question. 

b). Once the deployment of the cabi package has completed within the distsrv job window, DEACTIVATE the probe instantly and increase the java memory values for the cabi probe:
        java_mem_max = -Xmx256m
        java_mem_init = -Xms64m
      java_mem_max = -Xmx4g
      java_mem_init = -Xms1g

c). Right click on the cabi probe, go to the bottom “Edit” and copy to clipboard. 
Paste the output into a notepad file and take a copy of the probe address. 
- Example: /uim_domain/uim_primary_hub/uim_robot_cabi/cabi

d). Go to the UMP/OC Robot, press shift and right click on the wasp probe and select Raw Configure. Add a “New Key” under the setup section:   
- Key name: cabi
- Key Value: /uim_domain/uim_primary_hub/uim_cabi_robot/cabi

e). Apply and save the changes. Now ACTIVATE the cabi probe only and wait for the installation to complete.

** Once the cabi probe and cabi wasp probes are green, and both have a PORT / PID continue ** 

4. Upgrade the cabi bundled probe from 4.20 to 4.30. 

a). Drage and drop the 4.30 cabi package to the cabi robot. 
- This step will take a further 15-30 minutes to complete an upgrade.
- Open the cabi probe log file and monitor for the following message which indicates the upgrade is complete:  
[UserSynchronizationThread, cabi] Finished synchronizing users between UIM and CABI

b). Drag and drop the below package to the UMP / OC robot: 
- ump_cabi version 4.22 (or 4.21 if 4.22 is NOT available). 

c). Drag and drop the below packages to the CABI robot: 

- uim_unified_reporter_pack version 1.04
- uim_cabi_health_report_pack version 1.31
- uim_cabi_availability_report_pack version 1.00
- uim_core_dashboards_pack version 2.46
- uim_mcs_dashboards_pack version 1.0.0

Note: If any of the above packages are different versions, for now please deploy the highest version available within your local archive. 

d). Deactivate the cabi probe once the upgrade is completed as mentioned  by monitoring the log file in the earlier step. 
- Open the cabi probe raw configure -> setup -> Set the cabi_url to http://<CABI_Server_IP or hostname>/cabijs

** Once complete please open the CABIJS Web Console confirm the UIM Summary Dashboard loads. Open the OC and confirm the HOME tab CABI Dashboard loads **

If you see a data access error or a spinning wheel forever, please try the below steps.

1. Within the browser on the system where you are launching the OC, please disable the chrome browser samesite flag. 

a). In your browser session, navigate to chrome://flags

b). Set "SameSite by default cookies" from 'Default' to 'Disabled'

c). Then relaunch your Chrome browser, Clear browser cache from ALL time and retest.

If this continues, please review the below KB:

20.3.x-Operator Console Home page loads slowly, Group Trend Report redirects to CABI login screen, Data Access Error or Dashboard failed to load. (broadcom.com)