Configure Discovery Queues
If all discovery process probes are deployed on a single hub, communication of discovery data is automatically configured. However, if discovery probes are deployed to hubs other than the hub that hosts the discovery_server probe, ensure that discovery data can flow from those hubs up to the primary hub.
If all discovery process probes are deployed on a single hub, communication of discovery data is automatically configured. However, if discovery probes are deployed to hubs
otherthan the hub that hosts the discovery_server probe, ensure that discovery data can flow from those hubs up to the primary hub.
Flow is accomplished by setting up queues that handle the
- You can use a combination ofattachandgetqueues. Anattachqueue creates a permanent queue on a downstream hub. A correspondinggetqueue set up on the upstream hub is paired with eachattachqueue to retrieve messages from the downstream hub.
- Alternatively, you can usepostqueues. Apostqueue set up on a downstream hub sends a directed stream of messages to the upstream hub.
attachqueue is automatically set up on the primary hub to collect discovery data. Set up additional queues to collect discovery data from downstream hubs that host discovery_agent or any CTD-publishing probes. This list includes (but is not limited to):
- vmware 5.10 or later
- cm_data_import (typically deployed with discovery_server on the primary hub)
- rhev (Red Hat Virtualization)
Then set up a corresponding
getqueue (which retrieves messages from the
attachqueue) on the primary hub and on any hub that transfers the messages to another hub.
You can set up discovery queues in either Admin Console or Infrastructure Manager.
Follow these steps:
- Identify the hub on which you want to create a queue and open the hub configuration GUI:
- Admin Console:Expand the hub in the navigation tree and select its robot. Click the arrow next to the hub probe and selectConfigure.
- Infrastructure Manager:Expand the hus node and double-click the hub probe.
- Navigate toQueue ListorQueue.
- If you useattach/getqueues, set up the queues with the corresponding values:
- Attachqueue on the downstream hub:
- Name:attachDiscovery (or other name of your choice)
- Getqueue on the upstream hub:
- Name:getDiscovery (or other name of your choice)
- Address:address of the hub that has theattachqueue
- Queue:name of the correspondingattachqueue
- Bulk size:number of messages to be transferred together. (Optional: if you expect the queue to carry a significant number of messages, send them in bulk to improve performance.)
- If you usepostqueues, set up each queue with the corresponding values:
- Postqueue on the downstream hub:
- Name:postDiscovery (or other name of your choice)
- Address:address of the upstream hub
- Bulk size:number of messages to be transferred together
- Repeat the previous steps on all hubs that require a queue.
In small to medium deployments, a wildcard (*) subject, which carries any message, can simplify queue configuration. Use of a wildcard subject in large installations is not recommended.
For queue setup details, click the question mark or
Helpbutton in the configuration GUI.
The following illustration shows discovery queue configuration using
attach/getpairs. If you use a
postqueue configuration, the flow in the illustration would be similar, but you set up
postqueues instead of
attachqueues on all downstream hubs and you would not need to set up
When you have set up all required queues, run an automated discovery scan to confirm that the queues are operational. Review the list of discovered devices. In addition to local devices, this list would also contain devices that are only addressable from the secondary hubs.
Setting up other queues for alarms, QoS, and baseline data is a similar procedure of configuring attach and get queues. The subject of the queue changes as required by the type of data to be carried.