How do you remove old/retired Topology Agents

[Daniel Blanco]

So I have a corrupted hub.sds file and while looking thru the hub.log I noticed it was saying things like:

Dec 3 12:55:37:647 [2548] 1 hub: nametoip - /NMS/OLDCLINETA/clientA_HUB/topology_agent failed rc=4(not found)
Dec 3 12:55:37:647 [2548] 1 hub: nametoip - /NMS/OLDCLINETB/clientB_HUB/topology_agent failed rc=4(not found)

These hubs have been gone for many months so wondering how do we clean this up? How do we remove all references to old hubs and the discovery_agents b/c as per the log from today its still trying to find these old entries. 

I looked in the discovery_server probe utility list and don't see anything that allows to remove specifically 1 discovery agent.

What is the right way to do this? 

TIA...

------------------------------
Daniel Blanco
Enterprise Tools Team Architect
[e-mail]
------------------------------

[Gene Howard]

this could be caused by entries in the CM_DISCOVERY_AGENT table.
Review the data in this table and delete any old entries there for discovery_agents.

Also, make sure you do not have any old settings for tunnels or static mappings to these hubs.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Daniel Blanco]

Hi Gene,
So manually delete them via SQL queries to this table in the DB or are there any probe utilities that will do this for me?


------------------------------
Daniel Blanco
Enterprise Tools Team Architect
[e-mail]
------------------------------

[Daniel Blanco]

Okay I remember now. I had a case for this a long time ago. I can use the following:

select * from CM_DISCOVERY_AGENT order by hub

/* Find the da_id # in the table above and then enter it at the end of the line below to delete that discovery_agent
exec P_CM_REMOVE_DISCOVERY_AGENT @da_id =

exec P_CM_REMOVE_DISCOVERY_AGENT @da_id =56
exec P_CM_REMOVE_DISCOVERY_AGENT @da_id =207

Hopefully this is still the same method in 9.2.0's discovery server?
BTW Could I stop discovery_server, drop this table and then start discovery_server? Would it get re-populated once all the discovery_agents 'check-in' again? 
There are over 60 extra entries in this list today. Looking for easiest way to clean this up fully.

------------------------------
Daniel Blanco
Enterprise Tools Team Architect
[e-mail]
------------------------------

[David Michel]

there is 
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=33922

------------------------------
Support Engineer
Broadcom
------------------------------

[Daniel Blanco]

BTW just FYI for the clean up I just ran the

exec P_CM_REMOVE_DISCOVERY_AGENT @da_id =56

command on all the ID's after stopping the discovery_server, discovery_agent and topology_agent on the primary hub. Then started it all back up and everything got re-created. So all good for now..

------------------------------
Daniel Blanco
Enterprise Tools Team Architect
[e-mail]
------------------------------