DX Unified Infrastructure Management

  • 1.  Queues on customer HUBs

    Posted May 07, 2018 06:55 AM

    If you set up a new customer hub in a UIM installation where all alarm and DB handling are done centralized on the "top" hub.

    What are then the recommended queues/subject to set up.

    I don't want to have extra messages on the central hub so i guess the base lining not should go there.

    I also want separate queues for alarms. But I want to be able to use all functionality for UIM like discovery and so on.

    Please give some examples.

     

    Thanks in advance.



  • 2.  Re: Queues on customer HUBs

    Posted May 07, 2018 01:20 PM

    Pls go through the below .

    You can create dedicated queues for alarms and discovery info too

     

    Configure Discovery Queues - CA Unified Infrastructure Management - 8.5.1 - CA Technologies Documentation  



  • 3.  Re: Queues on customer HUBs

    Broadcom Employee
    Posted May 08, 2018 03:37 AM

    i do not recommend use asterisk (all subjects) i recommend that you specify subjects are as follows.

     

    QOS_MESSAGE

    QOS_DEFINITION

    probe_discovery

    alarm (*1)

     

    (*1) if your customer hub has local nas probe, you don't need to use hub queue to forward alarm message,

    because you could use alarm data forwarding feature nas probe has.

    The nas Setup Tab - CA Unified Infrastructure Management Probes - CA Technologies Documentation 



  • 4.  Re: Queues on customer HUBs

    Posted May 10, 2018 04:26 PM

    a queue for data_engine for example

    hub2_qos   & subject: QOS_MESSAGE,QOS_DEFINITION

     

    consider the potential need for nas auto operator rule/profile specific to this client

    two queues

    alarm_enrichment  & subject: alarm

    nas  & subject: alarm2

    forward/replication can be used to send the message up to the primary hub

    or another queue but not both

    hub2_alarms  & subject: alarm2

     

    figuring discovery_agent will need to be there

    probeDiscovery  & subject probe_discovery

    but I think this gets created when deploying the probe