DX NetOps

 View Only
Expand all | Collapse all

SDM - "BAD LINK DETECTED" tickets are not being associated with CI

  • 1.  SDM - "BAD LINK DETECTED" tickets are not being associated with CI

    Posted Jun 10, 2016 11:14 AM

    Hi All,

     

    Alarms for device's ports are not being signed to the CI registered into SDM, for eg: Event Code "0x10d11" Cause Code "0x1040a"

     

    PS: integration between Spectrum x SDM is working fine.

     

    To workaround this behavior I've created below Event Procedure:

     

    0x10d11 E 50 P "CreateEventWithAttributes(ReadAttribute({ C CURRENT_MODEL }, \

    { H 0x10069 } ), { H 0xffff0002 }, GetEventAttributeList() )"

    0xffff0002 E 50 A 3,0x1040a

     

    Now, ticket associations was fixed. However, I was not able to keep port's alarm and generate an alarm into device, if possible I'd like to keep event "0x10d11" (Critical) for the port and generate event "0xfff00002" (Critical) into the device.

     

    Or maybe, should have another way to do it, for eg customize integration file “service-desk-ticket-config.xml” forcing SDM when receive an alarm with cause code "0x1040a" to create a ticket associated with the device.

     

    Regards,

    Marcio



  • 2.  Re: SDM - "BAD LINK DETECTED" tickets are not being associated with CI

    Posted Jun 27, 2017 06:14 AM

    Please open a case with CA Support for this problem.