DX Unified Infrastructure Management

  • Private Community
 View Only

  • 1.  Fail maintenance mode with custom alarms

    Posted Sep 03, 2020 11:35 AM
    Good morning.

    Dear community, could you support me with the following topic:

    I have a custom alarm configured (robot is inactive) this alarm originates from the hub probe, a customization was made to change the alarm message, the problem is that when I try to put that alarm into maintenance mode it does not take it on counts and continues to alarm.

    I did tests with other equipment and the maintenance mode seems to work.


  • 2.  RE: Fail maintenance mode with custom alarms

    Posted Sep 04, 2020 04:36 AM
    - which type of maintenance mode? Via USM or via IM on robot level?
    - where did you customize the message (AO rule, script or pre-processing)
    - what "level" is your customized alarm?
    - what "hostname" has your customized alarm?
    Original Message


  • 3.  RE: Fail maintenance mode with custom alarms

    Posted Sep 07, 2020 12:59 PM
    - which type of maintenance mode? Via USM or via IM on robot level?
    USM
    - where did you customize the message (AO rule, script or pre-processing)
    prosecution
    - what "level" is your customized alarm?
    Review
    - what "hostname" has your customized alarm?

    The legend of the robot is inactive alarm was customized
    Original Message


  • 4.  RE: Fail maintenance mode with custom alarms
    Best Answer

    Posted Sep 07, 2020 01:23 PM
    Edited by Christopher Hackett Sep 11, 2020 02:55 PM
    You will need an alarm_enrichment customization to search for the dev_id in the cm_device table and update the alarm dev_id field; so that the dev_id field in the alarm corresponds with the hostname and not the hubname.
    There is a TEC doc: TEC1407211 that explains how to update the origin for this "robot inactive" message, You can use this example as starter to add the dev_id of your hostname/robotname.