QoS data from new secondary Hub is not visible in UMP

book

Article ID: 195714

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

We recently built out a secondary hub into our environment. The hub looks like it is functioning OK, we then deployed the AWS probe and created a template based on the probe data. That all seems to be correct. We do see the AWS information in the probe display but do not see AWS devices in the UMP. Is there something I might have missed on the config.

 

Cause

When hub-to-hub communication has been established after you deployed a new secondary hub, queues must be established on the primary and secondary hubs so that QoS data from robots under the secondary hub can flow to the primary hub. 

Environment

Release : 20.1

Component : Hub

Resolution

If a post queue is created on the secondary hub, messages will be sent with no acknowledgement.

If an attach queue is created on the secondary hub (recommended), a get queue must be created on the primary hub.

 

Instructions:

Create an Attach Queue on the secondary Hub

1. In the Admin Console breadcrumb, click uim.

2. In the hub list, click secondary.

3. In the right pane, on the Robots tab, click uimhub2 (your new secondary hub machine)

4. In the right pane, on the Probes tab, on the hub row, click the inline menu button and click Configure.
    The hub configuration window opens.

5. In the left pane, select Queue List.

6. In the right pane, under Queue List Configuration, click New.

7. Configure the queue entry fields as follows:

8. To save the hub configuration, click Save.

9. To close the Success dialog and the hub configuration window, click Close.

 

Create a Get Queue on uimserver (primary hub)

10. In the Admin Console breadcrumb, click uim.

11. In the hub list, click primary (your primary hub)

12. In the right pane, on the Robots tab, click uimserver (your primary hub machine)

13. On the hub row, click the inline menu button and click Configure.
      The hub configuration window opens.

14. The hub configuration browser window opens.

15. In the left pane, select Queue List.

16. In the right pane, under Queue List Configuration, click New.

17. Configure the queue entry fields as follows: (this is an example)

18. To save the new queue, click Save.

19. To close the Success dialog and the hub configuration window, click Close.

 

View the Status of the Queues

20. In Infrastructure Manager, open the hub probe on uimhub2 (your new secondary hub)

21. To view the toPrimary queue, click the Status tab.

22. To close the hub probe on uimhub2 (your new secondary hub), click Cancel.

23. In Infrastructure Manager, open the hub probe on uimserver (primary hub).

24. To view the fromClientA queue, click the Status tab.

25. To close the hub probe on uimserver (primary hub), click Cancel.

 

You can also use the Infrastructure Manager to create the queue, instead of using the Admin Console.