wasp probe not working post upgrade to 20.4 / taking a very long time to start

book

Article ID: 241806

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) Unified Infrastructure Management for Mainframe

Issue/Introduction

The Operator Console (OC) was updated to UIM version 20.4 but the wasp probe does not start and throws a Max. restarts in the wasp.log

How can we uninstall, reinstall and configure wasp in 20.40?

Cause

- wasp.cfg - possible corruption

Environment

Release : 20.4/20.41/20.42

Component : UIM OPERATOR CONSOLE - WASP & CORE

Resolution

Here are the steps to safely uninstall, reinstall and configure wasp in 20.40.

(All steps and results tested in UIM 20.4/20.41/20.42)

On the Operator Console (OC) robot,

1. Copy and save (backup) the entire wasp folder in a safe place for later restore of 1 or more sections if needed.

2. Deactivate wasp

3. Rt-click and delete the wasp probe.

4. Delete the existing-current wasp probe folder.

5. Restart the OC Nimsoft Robot service.

6. Redeploy the wasp probe v20.40.

7. Under the wasp <setup> section, set data_engine key in wasp.cfg to the NimBUS address of the data_engine on the Primary hub, 

  e.g., data_engine = /xxxxxx000523_domain/xxxxxx000523_hub/xxxxxxx000523/data_engine

8. wasp should start and get a port and a PID but if not, rt-click and Deactivate wasp.

9.Then Activate wasp.

10. Redeploy the following wasp webapps.

ump        20.40
wasp_alarmviewer_api      20.40
wasp_service_wrapper      20.40
nisapi_wasp       20.40
ump_operatorconsole      20.40
ump_cabi        4.25
ump_slm       20.40
ump_reportscheduler      20.10
mcsuiapp_portlet      20.40
ump_dashboard       20.40
ump_accountadmin      20.40
policy_management_ws      20.40

11. Set the loglevel to 5, and set a logsize of 50000.

12. Set the Java min/max memory settings to at least 2048 and 4096 respectively.

13. Update wasp.cfg ump_common section in wasp to the appropriate probe locations, eg., 

<ump_common>
   nas = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/nas
   sla_engine = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/sla_engine
   automated_deployment_engine = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/automated_deployment_engine
   discovery_server = /xxxxxxx000523_domain/xxxxxxx000523_hub/ABCDEFG/discovery_server
   lists_use_java_cache = false
   mcs_ui_app_url = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/mcs-ui-app/
   policy_management_ws = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/policy_management_ws
   maintenance_mode = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/maintenance_mode
   ems = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/ems
   mpse = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/mpse
   sla_engine = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/sla_engine
   udm_manager = /xxxxxxx000523_domain/xxxxxxx000523_hub/xxxxxxx000523/udm_manager
</ump_common>

14. Deactivate wasp.

15. Activate wasp.

16. Access the OC Portal and the pages should render as expected.

      http://<your_oc_robot>.xxx.xxxxxxxx.com/operatorconsole_portlet/overview

17. Manually deploy the OC components for OC 20.4 CU1 from here:

DX Unified Infrastructure Management - Hotfix Index
https://support.broadcom.com/web/ecx/solutiondetails?aparNo=99111410&os=MULTI-PLATFORM

18. Deploy only these packages listed below, manually to the OC Robot.

mcsuiapp_portlet-20.4.1.zip
policy_management_ws-20.4.1.zip
uim_reportscheduler-20.4.1.zip
ump_dashboard-20.4.1.zip
ump_operatorconsole-20.4.1.zip
ump_slm-20.4.1.zip
wasp_alarmviewer_api-20.4.1.zip

19. Activate wasp.

20. The wasp probe should then start up within 3-5 minutes without any significant delay.

Additional Information

wasp probe not working after upgrade to 20.4 and 'Group Management Failed' error in OC