DX Infrastructure Manager

Expand all | Collapse all

Alarm Notifier in Fault Tolerant 

  • 1.  Alarm Notifier in Fault Tolerant 

    Posted 09-27-2018 02:58 PM

    We have implemented alarm notifier for fault tolerance. we are using notifier to send a trap to another NMS whenever an alarm is created in spectrum. Below is the configuration in set, clear and update scripts for FT AN.

     

    On primary MLS: 

     

    if [ "$SANM_0X12c0a" = "20" ] 
          then 
                echo "Secondary SS is running" 
                echo "Precedence = $SANM_0X12c0a" 
                exit 0 

    else

          snmptrap < get all the information from the alarm and send a trap to another NMS>
    fi 

     

    On Secondary MLS:

    if [ "$SANM_0X12c0a" = "10" ] 
           then 
                echo "Primary SS is running" 
                echo "Precedence = $SANM_0X12c0a" 
                 exit 0 

    else

          snmptrap < get all the information from the alarm and send the trap to another NMS>

    fi 

    --------------------------------------------------------------------------------------------------------------------------------

     

    Now how it will work in the below scenarios:

     

    1.)  In case, when primary MLS server goes down completely, all spectroservers will point to backup MLS. In that case how alarms will be processed for the other primary spectoservers (having precedence value 10). Because secondary MLS will not process them as per the condition above.

     

    2.) If SS and archive manager are down on primary MLS, then how alarms will be processed ?

     

    Please share your thoughts on this.

     

    Thanks

    Bijender



  • 2.  Re: Alarm Notifier in Fault Tolerant 

    Posted 03-24-2019 09:36 AM

    Hello Bijender,

     

    We had a similar issue recently, and bellow is the resolution we applied.

     

    Instead of checking the value of the '$SANM_0X12c0a' variable we run MapUpdate on each MLS and get the current precedence of the secondary MLS.

    On the primary MLS, if the precedence is '20', the script proceeds to execute the rest of the commands in the script, else, the script is terminated.

    On the secondary MLS, it works vice versa, meaning the script continues on precedence '10', else is termianted.