Honored Contributor.. HPMST Honored Contributor..
Honored Contributor..
374 views

SHR nodes in ( Content pack component name ) is under Unassigned

Dear ALL,

in the HP operations agent data source summary table 

1- I Have most alot of nodes under Unassigned what is this mean ?

another questions 

2- How can I delete nodes from SHR ? 

0 Likes
5 Replies
Honored Contributor.. HPMST Honored Contributor..
Honored Contributor..

Re: SHR nodes in ( Content pack component name ) is under Unassigned

IS there any idea

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: SHR nodes in ( Content pack component name ) is under Unassigned

Hi,

The most likely scenario is that these nodes are no longer in the topology. Check whether the nodes appear under any of the OBR views in RTSM as they would become unassigned once they no longer appear in the respective views, e.g. SM_PA etc.

There is no supported way to remove these nodes currently in OBR - the nodes however will not be subject to any polling.

HTH

Honored Contributor.. HPMST Honored Contributor..
Honored Contributor..

Re: SHR nodes in ( Content pack component name ) is under Unassigned

Dear  C.M.S

Thanks alot for your reply what is the other views tha n SM_PA ? 

and can I customize this view from RTSM side to include more nodes ? 

0 Likes
Knowledge Partner
Knowledge Partner

Re: SHR nodes in ( Content pack component name ) is under Un

There is no supported way, but we found which tables to update to remove the unesseacry nodes through the postgres DB and have successfuly implemented it to remove nodes so they no longer appear in OBR for agents.

But yes you can change the view to include only the nodes you would like to sync to OBR

 

The view you need to look at for Agents is SM_PA, by default it will have any node which has an operation agent installed.

Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SHR nodes in ( Content pack component name ) is under Unassigned

Whilst technically possible modifying the views provided by OBR Content/ETL is NOT a supported activity. The views have been created in such a way to allow the efficient operation of OBR, e.g. not attempting to poll data from nodes where the collection would be unsuccessful (No agent installed etc.).

If you find you are having to modify views to achieve your requirements you might want to consider asking support to look at the issue with a view to product enhancement or perhaps to look at why the topology might be incorrect, or if customising then you could look at CDE to create your own custom content.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. 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.