NOTICE: Branded Content
NOTICE: Certain versions of content (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.
Operations Bridge Idea Exchange
cancel

Autoassignment should defer deploying until the certificate request is granted

In case a new Node is created in OMi several processes start in the background:
- Deployment of policies
- Agent health check
This is done independant from the certificate request status. OMi should take care of the certificate status of a node before starting actions which require a certificate in place.

OMi should be able to handle a node based on the certificate status:
- Assignment should only start in case the agent is installed and certificate is in place
- Node Inventory should be synced in case the certificate is granted (Agent version in Monitored Nodes)
- Agent Health monitoring should start only if the certificate is installed
- Error messages should be "human readable" in this area

Similar to 

https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM02721019


https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM03010911


https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01121479


https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01664072

Scenario:
Onboarding a new Agent with OMi

Workaround:
Manually correct all certificate issues in several areas of OMi

Unacceptable:
OMW and OML could handle this -> feature missing (removed?) from OMi

Required:

OMi should be able to handle a node based on the certificate status:
- Assignment should only start in case the agent is installed and certificate is in place
- Node Inventory should be synced in case the certificate is granted (Agent version in Monitored Nodes)
- Agent Health monitoring should start only if the certificate is installed
- Error messages should be "human readable" in this area

Similar to:

 https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM02721019


https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM03010911


https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01121479


https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01664072

3 Comments
Outstanding Contributor...
Status changed to: Waiting for Votes

Dear customers, if this is of interest to you, please vote...

Acclaimed Contributor.
Outstanding Contributor...
Status changed to: Already Offered

With OpsAgent 12.06, the agent topology will be created only after the certificate has been granted and hence the auto assignment will take place only after that. We hope this meets the requirement.

Thanks,

OpsB Idea Exchange Moderator