DX NetOps

Expand all | Collapse all

traps are not attaching to SBG event model or the spectrum model for which they were created

  • 1.  traps are not attaching to SBG event model or the spectrum model for which they were created

    Posted 2 days ago

    Hi All,
    We have used SBG to forward the trap from third party system such Oracle enterprise manager (OEM), Splunk etc to spectrum. but traps are not attaching to SBG event model or the spectrum model for which they were created, instead they are attaching to management server model (OEM, Splunk servers discovered in spectrum) in spectrum. what could be the reason for the same?

    Regards
    Rohit



  • 2.  RE: traps are not attaching to SBG event model or the spectrum model for which they were created

    Broadcom Employee
    Posted yesterday
    Hi Rohit,

    SBG uses 3 options to map the trap to an existing model or a new EventModel:
    1. Combination of variables 1-6 as the EventModel name (if it does not exist it is created)
    2. Variable 7 as the target model name
    3. Variable 8 as the target model ip address
    https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-3/integrating/southbound-gateway-toolkit/the-event-data-template.html

    When using IP address to map to an existing model, have in mind there are 3 IP address in a trap:
    1. The IP address the trap is sent from (this is part of the IP header. ex: 1.1.1.1)
    2. The IP address of the agent sending the trap (usually this one matches the first one, but let's consider different in our example: 2.2.2.2)
    3. Any IP address included in the trap varbinds (ex: 3.3.3.3)
    The second IP (2.2.2.2) is used to map the trap to EventAdmin model. That IP address must match the IP address assigned to EventAdmin at creation

    Then, when you map your varbinds in the AlertMap file, if your third IP (3.3.3.3) is mapped to variable 8, SBG will assert the resulting event to the model with that IP address.

    Maybe your AlertMap file and one trap example will help to understand the issue

    Regards







  • 3.  RE: traps are not attaching to SBG event model or the spectrum model for which they were created

    Posted yesterday
    Hi Jose,
    Thanks for response!
    only target hostname is coming in the trap which i tried to map it to variable ID 7 or 16 as noted in that tech doc. but it did not work.
    https://knowledge.broadcom.com/external/article?articleId=44103


    Below is content of alert map file. and sample screenshot. in current mapping hostname is showing variable ID 24

    #oraEMNGEvent oraEMNGEventNotifType

    1.3.6.1.4.1.111.15.2.0.3 0xfff00788 1.3.6.1.4.1.111.15.3.1.1.2(1,2)\
    #oraEMNGEventMessage
    1.3.6.1.4.1.111.15.3.1.1.3(3,0)\
    #oraEMNGEventMessageURL
    1.3.6.1.4.1.111.15.3.1.1.4(4,0)\
    #oraEMNGEventSeverity
    1.3.6.1.4.1.111.15.3.1.1.5(5,0)\
    #oraEMNGEventSeverityCode
    1.3.6.1.4.1.111.15.3.1.1.6(6,0)\
    #oraEMNGEventRepeatCount
    1.3.6.1.4.1.111.15.3.1.1.7(7,0)\
    #oraEMNGEventActionMsg
    1.3.6.1.4.1.111.15.3.1.1.8(8,0)\
    #oraEMNGEventOccurrenceTime
    1.3.6.1.4.1.111.15.3.1.1.9(9,0)\
    #oraEMNGEventReportedTime
    1.3.6.1.4.1.111.15.3.1.1.10(10,0)\
    #oraEMNGEventCategories
    1.3.6.1.4.1.111.15.3.1.1.11(11,0)\
    #oraEMNGEventCategoryCodes
    1.3.6.1.4.1.111.15.3.1.1.12(12,0)\
    #oraEMNGEventType
    1.3.6.1.4.1.111.15.3.1.1.13(13,0)\
    #oraEMNGEventName
    1.3.6.1.4.1.111.15.3.1.1.14(14,0)\
    #oraEMNGAssocIncidentId
    1.3.6.1.4.1.111.15.3.1.1.15(15,0)\
    #oraEMNGAssocIncidentOwner
    1.3.6.1.4.1.111.15.3.1.1.16(16,0)\
    #oraEMNGAssocIncidentAcked
    1.3.6.1.4.1.111.15.3.1.1.17(17,0)\
    #oraEMNGAssocIncidentStatus
    1.3.6.1.4.1.111.15.3.1.1.18(18,0)\
    #oraEMNGAssocIncidentPriority
    1.3.6.1.4.1.111.15.3.1.1.19(19,0)\
    #oraEMNGAssocIncidentEscLevel
    1.3.6.1.4.1.111.15.3.1.1.20(20,0)\
    #oraEMNGEventTargetName
    1.3.6.1.4.1.111.15.3.1.1.21(21,0)\
    #oraEMNGEventTargetNameURL
    1.3.6.1.4.1.111.15.3.1.1.22(22,0)\
    #oraEMNGEventTargetType
    1.3.6.1.4.1.111.15.3.1.1.23(23,0)\
    #oraEMNGEventHostName
    1.3.6.1.4.1.111.15.3.1.1.24(24,0)\
    #oraEMNGEventTargetOwner
    1.3.6.1.4.1.111.15.3.1.1.25(25,0)\
    #oraEMNGEventTgtLifeCycleStatus
    1.3.6.1.4.1.111.15.3.1.1.26(26,0)\
    #oraEMNGEventTargetVersion
    1.3.6.1.4.1.111.15.3.1.1.27(27,0)\
    #oraEMNGEventUserDefinedTgtProp
    1.3.6.1.4.1.111.15.3.1.1.28(28,0)\





  • 4.  RE: traps are not attaching to SBG event model or the spectrum model for which they were created

    Broadcom Employee
    Posted yesterday
    Hi Rohit,

    Variables from 1 to 16 are reserved for specific use and 17-9 for future usage of Broadcom.

    I guess the problem is you mapped:
    • oraEMNGEventActionMsg to variable 8 used as Target Address
    • oraEMNGEventRepeatCount used as Target Name
    • oraEMNGAssocIncidentOwner to variable 16 user as Target Name (case insensitive)
    If you specify a Target Name using fields 7 or 16 and a Target Address and one or both is not found, the appropriate error message is generated, and the event is not sent to any model

    The recommendation is that you map your varbinds starting on variable 100 and only map oraEMNGEventHostName to variable 16 to set the Target Model by Name (case insensitive)


    This would be my proposal for AlertMap:

    #oraEMNGEvent #oraEMNGEventNotifType
    1.3.6.1.4.1.111.15.2.0.3 0xfff00788 1.3.6.1.4.1.111.15.3.1.1.2(100,0)\
    #oraEMNGEventMessage
    1.3.6.1.4.1.111.15.3.1.1.3(101,0)\
    #oraEMNGEventMessageURL
    1.3.6.1.4.1.111.15.3.1.1.4(102,0)\
    #oraEMNGEventSeverity
    1.3.6.1.4.1.111.15.3.1.1.5(103,0)\
    #oraEMNGEventSeverityCode
    1.3.6.1.4.1.111.15.3.1.1.6(104,0)\
    #oraEMNGEventRepeatCount
    1.3.6.1.4.1.111.15.3.1.1.7(105,0)\
    #oraEMNGEventActionMsg
    1.3.6.1.4.1.111.15.3.1.1.8(106,0)\
    #oraEMNGEventOccurrenceTime
    1.3.6.1.4.1.111.15.3.1.1.9(107,0)\
    #oraEMNGEventReportedTime
    1.3.6.1.4.1.111.15.3.1.1.10(108,0)\
    #oraEMNGEventCategories
    1.3.6.1.4.1.111.15.3.1.1.11(109,0)\
    #oraEMNGEventCategoryCodes
    1.3.6.1.4.1.111.15.3.1.1.12(110,0)\
    #oraEMNGEventType
    1.3.6.1.4.1.111.15.3.1.1.13(111,0)\
    #oraEMNGEventName
    1.3.6.1.4.1.111.15.3.1.1.14(112,0)\
    #oraEMNGAssocIncidentId
    1.3.6.1.4.1.111.15.3.1.1.15(113,0)\
    #oraEMNGAssocIncidentOwner
    1.3.6.1.4.1.111.15.3.1.1.16(114,0)\
    #oraEMNGAssocIncidentAcked
    1.3.6.1.4.1.111.15.3.1.1.17(115,0)\
    #oraEMNGAssocIncidentStatus
    1.3.6.1.4.1.111.15.3.1.1.18(116,0)\
    #oraEMNGAssocIncidentPriority
    1.3.6.1.4.1.111.15.3.1.1.19(117,0)\
    #oraEMNGAssocIncidentEscLevel
    1.3.6.1.4.1.111.15.3.1.1.20(118,0)\
    #oraEMNGEventTargetName
    1.3.6.1.4.1.111.15.3.1.1.21(119,0)\
    #oraEMNGEventTargetNameURL
    1.3.6.1.4.1.111.15.3.1.1.22(120,0)\
    #oraEMNGEventTargetType
    1.3.6.1.4.1.111.15.3.1.1.23(121,0)\
    #oraEMNGEventHostName
    1.3.6.1.4.1.111.15.3.1.1.24(16,0)\
    #oraEMNGEventTargetOwner
    1.3.6.1.4.1.111.15.3.1.1.25(123,0)\
    #oraEMNGEventTgtLifeCycleStatus
    1.3.6.1.4.1.111.15.3.1.1.26(124,0)\
    #oraEMNGEventTargetVersion
    1.3.6.1.4.1.111.15.3.1.1.27(125,0)\
    #oraEMNGEventUserDefinedTgtProp
    1.3.6.1.4.1.111.15.3.1.1.28(126,0)\

    Be sure a model with name oraEMNGEventHostName exists in Spectrum.

    If the Target Name is not found, the EventAdmin model generates an Event that indicates that Spectrum has no models with the name <Target Name>

    Please update event 0xfff00788 with new variables numbers.

    Regards