DX Unified Infrastructure Management

  • 1.  Identical dev_src_id

    Posted Feb 21, 2017 08:07 AM

    Hi.
    I have a question about a device in CM_DEVICES. 

    As you can see from the screenshot, we have two devices with the same dev_src_id and one device is missing dev_ip. I suspect this is the reason why some alarms are not showing in USM.

    When I look at one alarm that is missing in USM, it has cs_id = -9999 so it isn't connected to a device. It should be connected to the device that has dev_ip = NULL.

    How can I correct the info in CM_DEVICES?



  • 2.  Re: Identical dev_src_id

    Broadcom Employee
    Posted Feb 21, 2017 09:39 PM

    Hello.

    UIM Database "NAS_ALARMS" table is being read by USM.

    The table has [dev_id].

    Here is an innner behavior finding out device for Owner of the alarm.

     

    NAS_ALARMS.[dev_id] <=> CM_DEVICE.[dev_id] <=> CM_DEVICE.[cs_id] <=> CM_COMPUTER_SYSTEM.[cs_id]

     

    As long as we able to resolve "owner of the alarm", the alarm is displayed in under that device (owner of the alarm)

     

    Hope this helps.

    Yu Ishitani



  • 3.  Re: Identical dev_src_id

    Posted Feb 22, 2017 02:44 AM

    Hello.

     

    Yes, this is the problem.

    We have some alarms  NAS_ALARMS that have a dev_id that doesn’t exist in CM_DEVICE.

    In NAS_ALARMS we have an alarm with dev_id =  D23DE0DD1E7ABE60BF1691ACD250F02EE

    This doesn’t exist in CM_DEVICES.

    The device itself exists in CM_DEVICES, but with a different dev_id.

     

    So the question is why the alarm gets a dev_id that doesn’t exist in CM_DEVICES.

     

    Regards

    Espen B Hanssen

     

     

     

     

    Fra: Yu_Ishitani

    Sendt: onsdag 22. februar 2017 03:40

    Til: Espen Bergvoll Hanssen <espen.hanssen@lindbak.no>

    Emne: Re:  - Re: Identical dev_src_id

     

    CA Communities <https://communities.ca.com/?et=watches.email.thread>

     

     

    Re: Identical dev_src_id

     

    reply from YU ISHITANI<https://communities.ca.com/people/Yu_Ishitani?et=watches.email.thread> in CA Infrastructure Management - View the full discussion<https://communities.ca.com/message/241960114?commentID=241960114&et=watches.email.thread#comment-241960114>



  • 4.  Re: Identical dev_src_id

    Broadcom Employee
    Posted Feb 22, 2017 04:20 AM

    Hello, Espen.

    Thank you very much for response.

    Can you please attach few examples of the problematic alarms ?

     

    Regards,

    Yu Ishitani



  • 5.  Re: Identical dev_src_id

    Posted Feb 22, 2017 04:43 AM
      |   view attached

    Hello.

     

    I have attached an Excel-document that contains the information from NAS_ALARMS, CM_DEVICE, CM_COMPUTER_SYSTEM and a query.

    The dev_id from NAS_ALARMS is not present in CM_DEVICES.

    I run this query to find the devices that match part of the hostname:

    select * from CM_DEVICE where dev_name like 'eli%'

    The result is listen under CM_DEVICES in Excel.

    I then run this:

    select * from CM_COMPUTER_SYSTEM where cs_id in (select cs_id from CM_DEVICE where dev_name like 'eli%')

    The result is listen under CM_COMPUTER_SYSTEMS

     

    In addition I ran this query:

    SELECT CASE WHEN dev.dev_id IS NULL THEN -9999 ELSE dev.cs_id END AS cs_id,

    cim.ci_id,

    cs.dedicated,

    cs.os_name,

    cs.os_type,

    nas.supptime,

    nas.assigned_at,

    ts.nimid,

    ts.visible,

    ts.nimts,

    ts.suppcount,

    ts.level,

    ts.message,

    ts.dev_id,

    ts.met_id,

    ts.subsys,

    ts.sid,

    ts.source,

    ts.hostname,

    ts.prid,

    ts.hub,

    ts.robot,

    ts.origin,

    ts.user_tag1,

    ts.user_tag2,

    ts.assigned_to,

    ts.assigned_by,

    ts.acknowledged_by,

    ts.custom_1,

    ts.custom_2,

    ts.custom_3,

    ts.custom_4,

    ts.custom_5,

    ts.i18n_token,

    ts.i18n_data,

    ts.time AS update_time,

    ts.closed,

    '' AS device_ctd_id,

    '' AS probe_address

    FROM NAS_ALARMS nas

    JOIN NAS_TRANSACTION_SUMMARY ts

    ON ts.nimid = nas.nimid

    LEFT JOIN CM_CONFIGURATION_ITEM_METRIC cim

    ON cim.ci_metric_id = ts.met_id

    LEFT JOIN CM_DEVICE dev

    ON dev.dev_id = ts.dev_id

    LEFT JOIN CM_COMPUTER_SYSTEM cs

    ON cs.cs_id = dev.cs_id

    WHERE ( 1=1

    )

    AND 1=1

    ORDER BY update_time DESC

     

    I’ve listed the one result that came with dev_id = -9999 under QUERY in Excel.

    We have had other alarms that we’ve had similar problems with, but they are not present at the moment.

     

    Regard

    Espen

     

    Fra: Yu_Ishitani

    Sendt: onsdag 22. februar 2017 10:21

    Til: Espen Bergvoll Hanssen <espen.hanssen@lindbak.no>

    Emne: Re:  - Re: Identical dev_src_id

     

    CA Communities <https://communities.ca.com/?et=watches.email.thread>

     

     

    Re: Identical dev_src_id

     

    reply from YU ISHITANI<https://communities.ca.com/people/Yu_Ishitani?et=watches.email.thread> in CA Infrastructure Management - View the full discussion<https://communities.ca.com/message/241960188?commentID=241960188&et=watches.email.thread#comment-241960188>

    Attachment(s)

    XLSX
    NAS_ALARM.XLSX   11 KB 1 version


  • 6.  Re: Identical dev_src_id
    Best Answer

    Broadcom Employee
    Posted Feb 22, 2017 04:54 AM

    Hello, Espen.

    Thank you very much for response.

     

    Unfortunately this might be an issue with sql_response probe or NAS probe.

    Please open a support case to move this forward, since community is not a space for us to track troubleshooting activities.

    (And note - Make sure your IT properties are masked on the data you attach especially in community.)

     

    Regards,

    Yu Ishitani