DX Infrastructure Management

Expand all | Collapse all

How can I change the discovery entries origin attribute

  • 1.  How can I change the discovery entries origin attribute

    Posted 10-07-2018 07:49 PM

    Hi


    I have one discovery_server and multiple discovery agent probes with the same origin 'HIPPO' set on each hub and it own robot. I am running UIM 8.5 , discovery_server and discovery agent version 8.5.

    Some of the hub is monitoring multitenant environment using remote monitoring  probe ( snmpcollector, snmptd, net_connect, pollagent, interface_traffic) deploy on it .

    The QOS data I have use qos_processor to enrich the Origin field so now it show 'HIPPO' and 'TenantOrigin' in the USM origin field.

    Because some device are not publishing QOS it show the Hub origin 'HIPPO' discovered by the discovery_agent.

     

    How can I change the discovery entries origin attribute so that when I create a USM group field I just need to filter it by Origin.



  • 2.  Re: How can I change the discovery entries origin attribute

    Posted 10-08-2018 10:20 AM

    one option is to set an origin override at the robot via > controller configure > setup > advanced.



  • 3.  Re: How can I change the discovery entries origin attribute

    Posted 10-09-2018 08:21 PM

    The robot was set to origin 'HIPPO' it is using remote monitoring  probe ( snmpcollector, snmptd, net_connect, pollagent, interface_traffic) to monitor multiple tenant .

     

    Yesterday I have a created a xml for cm_data_import  that contains minimal structure and import it after discovery_server and discovery_agent completes.

    The xml I prepare contains all the thousands of devices being monitored regardless it is monitored for alarms or QOS.

     

    <Devices>
    <Device>
    <PrimaryDnsName>Tentent1 SHORT HOSTNAME1</PrimaryDnsName>
    <UserAlias>cm_data_import_SHORT HOSTNAME1</UserAlias>
    <Origin>TenantOrigin1</Origin>
    <PrimaryIPV4Address>1.2.3.4</PrimaryIPV4Address>
    <PrimaryDnsName>Tentent2 SHORT HOSTNAME3</PrimaryDnsName>
    <UserAlias>cm_data_import_SHORT HOSTNAME3</UserAlias>
    <Origin>TenantOrigin2</Origin>
    <PrimaryIPV4Address>1.2.3.5</PrimaryIPV4Address>
    </Device>
    </Devices>

     

    But I am not sure if this is the right approach as previously without using much cm_data_import I am able to access the Relationship Viewer is by choosing Launch Relationship Viewer from the Actions menu in the Unified Service Manager (USM) portlet.

    Currently it is not showing up at the action menu for all the groups, but when I add a Relationship Viewer portlet to a UMP page it shows the default view where I can find lots of device that is in the groups showing up.



  • 4.  Re: How can I change the discovery entries origin attribute

    Posted 10-10-2018 02:53 AM

    snmptd probe create devices of trap sender, and those origin could either be robot's origin or hub (that manages to robot) origin.

    I don't know how to tweak it.



  • 5.  Re: How can I change the discovery entries origin attribute

    Posted 10-11-2018 11:10 AM

    I am currently having problem with topology on How do I rebuild or clean up topology data  when I used cm_data_import with all the device data imported to achieve the view intended. For those from the snmptd I did use cm_data_import to create a cm_device entry and in turn create a cm_computer_system with the fake data. Was intending to use nas enrichment to How can I enrich alarm2 message to map in USM device imported by cm_data_import or gather by dicovery_agent to the cm_device entries dev_id. I use the Imported alarms not shown in USM  with nas test alarm which works with 'alarm' subject and it seem to work and map to the fake devices. But now without confirmation first that the topology view was affected by the cm_data_import I can't use the alarm mapping as I running remove_all_master_devices everyday I come to work it when I hit some problem that never happen previously like the Launch Relationship Viewer from the Actions menu.