MOI APPLIANCE CONTROLLER DUMP FILE NEEDS ANALYSIS

book

Article ID: 142916

calendar_today

Updated On:

Products

CA Mainframe Operational Intelligence

Issue/Introduction

Per our cust the CA-Broadcom Support Case was opened to forward the MOI Appliance Controller DUMP

from Production to one of our CA-Broadcom field colleagues for analysis. Our field colleague   was aware

of it.

Cause

-

Environment

Release : 2.0

Component : MF OPERATIONAL INTELLIGENCE

Resolution

The MOI Appliance Controller DUMP was forwarded to the MOI SME (Subject Matter Expert) and Level 2 Support to
review it. Succinctly they said thus--full comments  forwarded to cust:
 
 
We have reviewed the MOI DUMP that you uploaded and have not been able to find any conclusive reason why your
microservices became unhealthy.  The reboot fixed your issue and reset the environment. If you are still having     the
unhealthy container problem, please let us know immediately in the future by opening another case if this same    be-
havior occurs. Create an MOI DUMP before any reboot is attempted and notify MOI Support immediately         before
rebooting so that we can actually look--at that point in time--into the environment where the unhealthy containers  are
appearing.
 
We also see that you are currently on MOI 2.0.02.  Our STRONG recommendation is that you consider  upgrading to
MOI 2.0.05. Please contact us if needed with regard to this upgrade effort.  An upgrade would take advantage        of
many new improvements to MOI.
 
-

Additional Information

CA MOI 2.0 techdocs library starts here:

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/intelligent-operations/ca-mainframe-operational-intelligence/2-0.html 

-

 

CA MOI 2.0.05 techdocs library starts here:

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/intelligent-operations/ca-mainframe-operational-intelligence/2-0-05.html