DX NetOps

Expand all | Collapse all

blade status unknown and EventDisp

Jump to Best Answer
  • 1.  blade status unknown and EventDisp

    Posted 03-16-2018 01:36 PM

    We're on 10.2.3 as of last Friday.  We see blade status unknown when a site is down event though switches are suppressed.  We noticed on 10.2.1 also. 

     

    See that this was resolved in 10.2.0 by some change to EventDisp file.  So wonder if we just don't have the changes in our EventDisp file.

     

    Is this the EventDisp file under Custom/Events folder or somewhere else?  Wonder if we can get the statements to add to check if EventDisp has the modifications whatever they are?

     

    Symptom: Alarm view shows "Blade Status Unknown" secondary alarm on suppressed devices even with the default 'hide symptom alarms' filter. Resolution: Fixed the Event configuration in the EventDisp to avoid this.

    (10.2.0, DE198468, 00199996)



  • 2.  Re: blade status unknown and EventDisp

    Broadcom Employee
    Posted 03-16-2018 04:16 PM
      |   view attached

    Hi Jon,

                    You should have this in your SS/CsVendor/Cabletron/EventDisp:

     

    #Chassis Extended Fault Isolation

    0x00010f68 E 20 C 0x00010f69 R CA.EventCondition, "default" , "0x00010f72

    0x00010f69 E 20 A 3,0x00010f69 R CA.EventCondition, "default" , "0x00010f71"

    0x00010f6a E 20 C 0x00010f69

    0x00010f71 E 20 A 2,0x00010f71

    0x00010f72 E 20 C 0x00010f71

     

    If you do, check your custom/Events/EventDisp and see if you customizations to these events which may be causing the issue.

     

    Cheers

    Jay



  • 3.  Re: blade status unknown and EventDisp

    Posted 03-19-2018 03:50 PM

    Hi Jay,

    Here is what is in our eventdisp from Cabletron folder.  None of these event numbers show up in the custom/Events/Eventdisp file at all.

     

    When I go into the ECE I see Custom as Author for 0x00010f69 but this hex event number does not even show up in custom/Events/Eventdisp file at all so not sure if it was edited momentarily then put back to original as the event looks same as your output.

     

    I went ahead to copy and paste your output into my eventdisp file under Cabletron path to note any difference.

     

    From Cabletron path - eventdisp file

    #Chassis Extended Fault Isolation

    0x00010f68 E 20 C 0x00010f69 R CA.EventCondition, "default" , "0x00010f72

    0x00010f69 E 20 A 3,0x00010f69 R CA.EventCondition, "default" , "0x00010f71"

    0x00010f6a E 20 C 0x00010f69

    0x00010f71 E 20 A 2,0x00010f71

    0x00010f72 E 20 C 0x00010f71
    0x00010f8c R CA.EventCondition, "({v 2} >= {I 3} && {v 1} < {I 3})" , "0x00010f68 -:-","({v 1} == {I 3})" , "0x00010f69 -:-","({v 2} <= {I 3} && {v 1} > {I 3})" , "0x00010f6a -:-"

     

    #Clear Module Pulled Consolidated Event

    0x00010fa8 E 20 C 0x00010f6d

     

    Thanks.

    Jon V.



  • 4.  Re: blade status unknown and EventDisp

    Broadcom Employee
    Posted 03-20-2018 10:48 AM

    Hi Jon,

     

    Maybe it is something with your Alarm Filter?  Can you please check to make sure the alarm filter has "Hide Symptoms" under the State tab of the Alarm Filter instead of "Show Symptoms" 

     

    Best regards,

    Glenn



  • 5.  Re: blade status unknown and EventDisp
    Best Answer

    Posted 03-30-2018 04:29 PM

    We're not sure why this behavior was occurring.  We noticed it when a complete site was down.  We did see the blade status unknown alarm clear when a device came back up.  It was just whena whole site was down the alarm was not being hidden.  Look at contactlost_gray (if memory serves) and it was collecting that alarm.  Ended up editing site_down condition to collect that alarm and we haven't seen it since.  Manager performed some customizations so it must have been related to that but configured around it.