DX NetOps

Expand all | Collapse all

Interfaces Alarms on the Device.

  • 1.  Interfaces Alarms on the Device.

    Posted 07-11-2013 02:22 AM

    Hi all,
    Using Spectrum... on windows.
    When the device "BiB...Model No:AVS920W+" interface's down, customer wants these alarms on the 'Device' in spectrum.
    For this we tried, in the interfaces ->component details ->Alarm configuration.."Generate Alarm on Port" & "Generate Alarm on Device" set both to 'Yes'.
    Also set the following Attributes on the interfaces
    PollPortStatus 0x1280a.....No
    ok_to_poll 0x11dd8.....No
    AlarmOnLinkDownTrap 0x11fc2.....check status(1)
    AssertLinkDownAlarm 0x12957.....yes
    GeneratePortStatusAlarms 0x12a54.....yes
    But spectrum didn't created alarm on the device.
    Any help??


  • 2.  RE: Interfaces Alarms on the Device.

    Posted 07-11-2013 02:32 AM
    Hello Umair,

    The following is an example of an Event Procedure that will take an event from an Interface model and forward it to the associated Device model using the Device_Mdl_Handle attribute 0x10069 (which contains the value of the device model handle associated with the Interface model) from the Interface model and create a new event on the associated Device model.

    0xffff0000 E 50 P " \
    CreateEventWithAttributes( \
    ReadAttribute( \
    { C CURRENT_MODEL }, \
    { H 0x10069 } ), \
    { H 0xffff0001 }, \
    GetEventAttributeList() )"

    This would transfer the event 0xffff0000 from the interface model to the device, as event 0xffff0001. All varbinds from the original event 0xffff0000 will also be present on event 0xffff0001 on the device.



  • 3.  RE: Interfaces Alarms on the Device.

    Posted 07-11-2013 05:51 AM
    Thanks Kalyan.
    Now also set the attribute 'Device_Mdl_Handle attribute 0x10069......0xea601a2f' on the interface.
    But not found event 0xffff0000...Plz explain how we create it on the associated device.


  • 4.  RE: Interfaces Alarms on the Device.

    Posted 07-11-2013 05:58 AM

    The event 0xffff0000 is just a test event. This needs to be replaced with your event code comming on the interface model.0xffff00001 is the new event which you need to create from ECE with the same event message and alarm title as 0xffff0000.

    Remove the alarm for the default event comming on the interface model.