Default hub queue configuration on secondary hub

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After installing a secondary hub, queues need to be configured on the new hub and the primary hub (or an intermediate hub) to get critical messages flowing up to the primary hub.

What are the default queues that I would need to setup when adding a new hub to my UIM infrastructure?

Environment

UIM Server any release

Resolution

 

After you have installed the hub software you will want to minimally add queues to handle the following subjects for a base configuration to the newly created hub:

alarm

QOS_MESSAGE

QOS_DEFINITION

QOS_BASELINE

probe_discovery

ROBOT_NIS_CACHE (for UIM 23.4)

To create:

In Infrastructure Manager > double click the hub probe on newly added hub machine > select the Queues tab > click New > create each of the following:

Example:

Click Apply > OK 

Next in Infrastructure Manager > double click hub probe on your primary hub > select the Queues tab > click New to create a connecting queue for each of the new hub queues with the following as an example:

Note:  To pull more messages with each message posting on the queue, you can override the hub default bulk size (100) by specifying a larger bulk size.  With hub versions 7.x and later you can safely specify a value of 2000.  This will help the corresponding attach queue on the new hub to drain faster if there are a large number of messages on these queues.

The resulting queues:

Click Apply > OK 

After the hub probe has restarted, you can then check the status of the queues by clicking on the Status tab.

Additional Information

Alternatively a single attach queue can be created on the secondary hub using just * which will send all messages to the upstream hub. Example:



If you have enabled auditing in your UIM infrastructure, then you would also want to add audit messages to one of the configured attach queues on the secondary hub.

If you need to define Time Over Threshold alarms on any probes running on the new hub or robots managed by the new hub, then you would have to install a nas probe on the new hub.  In this case, you should not define an attach queue to send alarm messages to the primary hub.  You should also set up uni-directional forwarding from the nas on the new hub to the nas on the primary hub.