DX NetOps

  • 1.  SDNotifier Difference Time(Hour)

    Posted 10-28-2018 08:52 AM
      |   view attached

    Hi All, 


    We are currently having problem with SDNOTIFIER service.


    After to upgrade the CA Spectrum  to 10.3 version, the SDNOTIFIER is 4 hours ahead from my DST.


    Is there any procedure that I have to do to solve it?


    This difference time is impacting the SDNOTIFIER to run properly and open the tickets.

  • 2.  Re: SDNotifier Difference Time(Hour)

    Posted 10-28-2018 09:01 AM

    I already did this procedure without success:


    Will the Brazil DST change in 2018 affect CA Spect - CA Knowledge 

  • 3.  Re: SDNotifier Difference Time(Hour)

    Broadcom Employee
    Posted 10-29-2018 09:23 AM

    Hello Flavio,


    When did you upgrade the CA Spectrum to 10.3? Was it before 10/21/2018? Or after?

    The CA Spectrum 10.3 already supports the new DST time.


    Did you upgrade the SD_Notifier binary files after you upgraded to 10.3 release?

    Reinstalling or Upgrading CA Spectrum - CA Spectrum - 10.3 - CA Technologies Documentation 




  • 4.  Re: SDNotifier Difference Time(Hour)

    Posted 10-29-2018 09:42 AM

    Hello Silvio, 


    I did the upgrade on last saturday.


    I did a new creation with the new SDNotifier but the difference time persist.

  • 5.  Re: SDNotifier Difference Time(Hour)

    Broadcom Employee
    Posted 10-29-2018 10:42 AM

    Hi Flavio,


    What is the version of AlarmNotifier.exe binary file located in $SPECROOT/Notifier/sd_notifier/ directory?




  • 6.  Re: SDNotifier Difference Time(Hour)

    Posted 10-29-2018 11:06 AM



    Where can I found this information?

  • 7.  Re: SDNotifier Difference Time(Hour)

    Posted 10-29-2018 11:58 AM



    I fix this problem doing the Oc_components update.


    But after to do that, the SDnotifier not opens ticket using the policy defined (custom policy SDnotifier).


    The alarm notification run properly without open ticket in SDM.


    Alarm Notification from SPECTRUM

    Alarm SET:

    Date: 10/29/2018
    Time: 12:44:13
    Mtype: EventModel
    ModelName: procedbhm1
    AlarmID: 826476
    Severity: CRITICAL
    ProbableCauseID: 6330070
    SpectroSERVER: vvcewpspctrm01
    Landscape: 0x100000
    ModelHandle: 0x101417
    ModelTypeHandle: 0x3dc0001
    AlarmState: EXISTING
    Acknowledged: FALSE
    UserClearable: TRUE
    AlarmAge: 4



    An event from UIM's Spectrum Gateway Probe was received and caused this alarm.



    1) Refer to information in the Alarm Details and associated Event Message.

    2) Using the Alarm Title, identify the specific type of alarm.

    3) Additional alarm details may be obtained by viewing the alarm in UIM or Unified Management Portal. Consult the UIM Alarm Service for more information on this condition.

    EventMessage: seg 29 out, 2018 - 12:44:13 - seg 29 out, 2018 - 12:44:13 - UIM's Spectrum Gateway Probe (Spectrum gtw)

    Critical Alarm generated with the following details:
    [UIM Nimsoft] - CRITICAL ALARM - High Capacity Partition Utilization - Free Space on Device /u01 is (7%)
    Source: procedbhm1
    Level: 3
    Suppression Key: disk//u01
    Probe Name: cdm
    Origin: vvcewpnimhub02
    UIM_Alarm_ID: GH41377285-91626
    Alarm Source: 2
    ChangeOwner: 3
    Trouble Ticket ID:
    Trouble Shooter:
    User Tag 1: PRODUCAO
    User Tag 2: dashboard
    Custom 1:
    Custom 2:
    Custom 3:
    Custom 4:
    Custom 5:
    Spectrum Event ID: 0x06330070



    Is there another point to verify?


    PS: I'm using dynamic global collection to filtered the elements that can be open ticket.

  • 8.  Re: SDNotifier Difference Time(Hour)

    Broadcom Employee
    Posted 10-29-2018 04:19 PM

    The reason the sd_notifier is no longer creating the tickets is because the OOB ServiceDesk scripts (ServiceDeskSetScript, ServiceDeskUpdateScript, and ServiceDeskClearScript) were deleted and the Notifier scripts were being used (SetScript, UpdateScript, and ClearScript).