DX NetOps

 View Only
  • 1.  SANM - Filter alarms by impact value

    Posted Jul 10, 2015 10:34 AM

    Hi guys, I didn't found any way to filter alarms by its impact under SANM, is there any way to do it?



  • 2.  Re: SANM - Filter alarms by impact value



  • 3.  Re: SANM - Filter alarms by impact value

    Posted Jul 10, 2015 11:42 AM

    Hello Moreno,

     

    I don't think we have a way to add one more additional parameter under a sanm filter.



  • 4.  Re: SANM - Filter alarms by impact value

    Posted Jul 10, 2015 12:19 PM

    Hi Kothapalli,

     

    My cust would like to open tickets only to alarms with impact higher than some value, for eg. "1000"

     

    I could filter them under SetScript on alarm notifier, however, impact value is calculated using two alarm's attribute: 0x12a6b / 0x1298a, as you can see below:

     

    " $SPECROOT\tomcat\webapps\spectrum\WEB-INF\alarm\config\column-alarmimpactseverity-config.xml"

     

    <content>

        <expression>

          ( (attr(0x12a6b)) != null ? attr (0x12a6b) : attr (0x1298a) )

        </expression>

        <renderer>

     

    It would be usefull if we could filter alarms by its impact, because we intend to treat only alarms with higher impact.

     

    Thanks!!!



  • 5.  Re: SANM - Filter alarms by impact value

    Posted Aug 05, 2015 02:11 PM

    My solution is use SetScript. I'm sure there is a way to do this with bash, but I find it easier to use a Perl script instead. Below is the bit where I calculate the impact:

     

    # Get alarm impact
    my $impact = 0;
    my $combinedimpact = $ENV{'SANM_0X12A6B'} || $ENV{'SANM_0X1298A'} || 0;
    if ( $combinedimpact =~ /^2.0.1.0.0.0.1.0.1.0.(.*?)\.(.*?)\.(.*?)\.(.*?)\./ ) {
      my $hex = sprintf( "0x%02s%02s%02s%02s", $4, $3, $2, $1 );
      $impact = hex $hex;
    }
    


  • 6.  Re: SANM - Filter alarms by impact value

    Broadcom Employee
    Posted Jun 26, 2017 01:08 PM

    Thanks for using the CA Community!  It looks like your question has been answered so we are closing this thread out.  If you have additional questions, please feel free to contact us again.