UIM - CABI is not available or accessible in OC
search cancel

UIM - CABI is not available or accessible in OC


Article ID: 212847


Updated On:


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


OC Reports displays "CABI is not available or accessible

Validated that CABI is up and running (http(s)://<cabi_robot>/cabijs) successfully logged in (superuser:superuser)



Any CABI version


This issue can present itself in various scenarios:

Scenario 1. 'cabi/api/server info  503' reported in the Archive (.*har) file

Launch Chrome and login to OC, Launch Chrome developers tools (F12), Click on Reports to produce the issue, Review Console messages as shown below and noted if 'cabi/api/server info  503' is seen.

HTTP error 503 means Service Unavailable, but it was already confirmed the cabi is up and running. Strangely the ip address in the POST request, match the cabi robot ip address.

It may happen that a specific service didn't start correctly, hence the error 503.

NOTE: Another scenario when the same error 503 has been observed is when using an external URL to access CABI Server, but the cabi robot has blocked the traffic to the public ip. The cabi can be accessed using the private ip/hostname/fqdn, but not when using the public fqdn/ip. To resolve this particular scenario, the rule blocking the traffic to the public ip it needs to be removed from the firewall.

Scenario 2. cabijs/client/visualize.js displays Results with 0 instead of 200 in the Archive (.*har) file when CABI is configured with self-signed certs




Scenario 1

1. Deactivate cabi probe and wasp probe on cabi robot. Delete the cabi log (nimsoft/probes/service/cabi/cabi.log) and wasp log (nimsoft/probes/service/wasp/wasp.log)
2. Deactivate wasp probe on OC robot, and delete the wasp log (nimsoft/probes/service/wasp/wasp.log) and operatorconsole logs (nimsoft/probes/service/wasp/operatorconsole.log.*)
3. Activate the wasp probe on OC robot
4. Activate the cabi probe and wasp probe in cabi robot

Scenario 2

1. Launch the browser and accept the risk for the following link:  https://<CABI_Server_IP or hostname>/cabijs/client/visualize.js.

2. Click on OC Report and validate the issue is resolved

Note:  Configure CABI and OC with CA Auth. Signed certificates to avoid this issue

If problem persist for either above scenario, open a support incident

Additional Information

Operator console shows CABI is not available or accessible

Using an External URL to Access CABI Server