Cloud Optimizer Practitioners Forum
cancel

(CO) Support Tip: How does the "INSTANCE_DELETION_THRESHOLD" parameter work with CO and OMi/OMx?

Highlighted
Mark_Butler
Micro Focus Expert

(CO) Support Tip: How does the "INSTANCE_DELETION_THRESHOLD" parameter work with CO and OMi/OMx?

Hello CO Community,

As you may have seen with previous posts or answers to questions, there is a new Parameter that was introduced with OMi Management Pack for CO verion 1.24 but fully tested with OMi Management Pack for CO version 1.25.  This parameter is the "INSTANCE_DELETION_THRESHOLD" parameter.

This parameter was instroduced as part of the following defect:
QCCR8D83763 CO node discovery adds and deletes nodes from OML/OMi server frequently

There are two parts to the Cloud Optimizer (CO) and OMi/OMx integrations.

  • CO Collect data from environment and places it in the CO database.
  • OMi/OMx Policies query CO database and forwards information to the OMi/OMx environment.

The defect QCCR8D83763 is encountered when the discovery process fails to properly discover an instance to update the information within the Cloud Optimizer (CO) database.  When this occurs, the deletion of the instance can occur within the OMi/OMx environment.

Rather than delete the CI, this parameter acts as a counter which decrements until it reaches '0'.  This parameter is configurable and can be increased using the "ovconfchg" command.

More information about this paramter and how to set it is included within the following knowledge article.

KM02942064 - How does the "INSTANCE_DELETION_THRESHOLD" parameter work with Cloud Optimizer and OMi/OMx?
https://softwaresupport.hp.com/km/KM02942064

There are ongoing investigations in this area.  More information about additional options may be available at a later time.

I hope that this information is helpful.

Have a wonderful weekend!

Mark

---
Mark Butler
Micro Focus SW Support Engineer
https://softwaresupport.hpe.com/