DX Infrastructure Manager

Expand all | Collapse all

Update Enriched origin -> cm_computer_system?

Jump to Best Answer
  • 1.  Update Enriched origin -> cm_computer_system?

    Posted 11-24-2019 06:59 AM
    Edited by Luc Christiaens 12-09-2019 09:33 AM
    Environment: uim 9.20 on w2016 and sql 2016
    MSP with several clients, each with their own origin.
    But some probes, like vmware, ibmvm and ibm-svc are monitoring devices from several clients. (and not all these vmware guests have a robot installed)
    - we created a pre-processing LUA script to set the correct origin on alarms for these 3 probes.
    - We created also a qos_processor enrichment.rb script to set the correct origin on qos for those 3 probes.
    - We defined UMP accounts for each Client, and defined that they only can see their origin.
    - In USM we created a group for each customer based on the origin.
    But: when I login with a client account, I can see all devices in Inventory BUT no vmware device in the USM group.
    The devices monitored by the 3 generic probes (vmware, ibmvm and ibm-svc) are defined in cm_computer_system with the old/wrong origin of the hub even if all alarms and qos are enriched correctly.
    Question: can we define a rule in discover_server.cfg where we say that for the indicated probes (vmware,..) we want the EnrichedOrigin field set into the cm_computer_system origin field?
    (because, as a test, I did a manual override of some devices in the cm_computer_system table and at that moment the USM group is displayed correctly when I logon with a client account)
    Did anyone encounter the same problem and found a solution?
    Or did somebody has some experience with the correlation in discovery_server?
    Thanks, Luc

  • 2.  RE: Update Enriched origin -> cm_computer_system?

    Posted 11-24-2019 12:42 PM
    Hi Luc,

    Is there some reason that the hub/robot origin override cannot be used to control the origin names?


    Support Engineer

  • 3.  RE: Update Enriched origin -> cm_computer_system?

    Posted 11-24-2019 12:55 PM
    Hi Steve,
    This robot with vmware/ibmvm is controlling multiple clients guests.
    The client guest origin can be assigned thanks to guest naming convention that is used in the alarm and qos enrichment
    Thanks, Luc

  • 4.  RE: Update Enriched origin -> cm_computer_system?

    Posted 12-11-2019 09:23 AM
    Hi Luc,
    Hi Stephen,
    I ran in exactly the same issue since many years. Centralized monitoring probes (like vmware, sql_response, net_connect, icmp etc.) monitors hundred devices of several customers. For alarm messages I can manipulate the origin by pre-processing scripts within the NAS. For qos messages I can manipulte the origin by qos_processor. But how i can do this with discovery server?

    Some years ago there was a topic on the roadmap that one should be able to define the origins in the probe profiles. This would solve this isuue. However, this topic has not been present anywhere for some time.

    Maybe someone of the Broadcom staff can say something about this.

    SInce 2006 experience with:
    NimBUS | SDP | UMP | UIM | DX Infrastructure Management
    API | SDK | Probe Development
    Nimsoft | CA | Broadcom

  • 5.  RE: Update Enriched origin -> cm_computer_system?
    Best Answer

    Posted 12-11-2019 09:29 AM
    I have an issue open that is with dev. for the moment.
    As a bypass (because not sure if we will receive a solution in time) I wrote a Perl script that will search all devices that are in need of enrichment in cm_computer_system and creates the needed sql update statements

  • 6.  RE: Update Enriched origin -> cm_computer_system?

    Posted 11-27-2019 01:50 AM
    Edited by Luc Christiaens 11-27-2019 04:11 AM
    -- removed update --