Need detail steps about create the events in BSM/OBM based on the SNMP Traps , MIB"s and OID's

Hi Team,

I have created the SAN Storage policy in BSM/OBM console.

I got SNMP Traps from SAN Storage servers in BSM/OBM console event browser.

Storage team shared the MIB file to create the events.

Please help me detail steps about to create the events based on MIB files ,  by using MIB file how we can frame the OID's Please help me with an example of creating the events.

please help me how we can decide the OID's by using MIB file   let me know an example.

  • Suggested Answer

    0  

    Hello,

    To create a policy from a SAN MIB file, you can use the mib2policy script located at:
    /opt/OV/contrib/mib2policy/bin/mib2policy.sh.

    This tool generates a policy, but you'll only see conditions where NOTIFICATION_TYPE and TRAP_TYPE are defined. This limitation is due to how SNMP MIBs are structured, not an issue with the script itself.

    As you've mentioned, your vendor's hardware monitoring software should forward SNMP traps to a server running the Operations Agent with a trap interceptor policy. The Operations Agent converts these traps into OMi events, feeding them into the event stream for processing by OBM.

    Here’s my suggested approach:

    1. Configure the SAN to forward all events to OBM.
    2. Use the OBM console to filter and export the events to a file.
    3. Identify unique events and consult with the SAN administrators to determine which ones are critical.
    4. Build SNMP policy conditions based on the SAN administrators' input.

    For more details, refer to the product documentation: Micro Focus Operations Bridge Manager - SNMP Traps.

    Thanks!

  • 0 in reply to   

    Hi Duncan,

    Thanks for your  reply.

    Can you please help me  steps to create the events in BSM/OBM console , here we are using SNMP V2.

    In BSM/OBM i saw the events , can you give me and example how i can create the meaning full event based those events.

  • Suggested Answer

    0   in reply to 

    Hello there,

    I feel there is enough information above to make this work.  I guess the one part that is missing is the SNMP prolicy itself - lets call it step 1.5:

    1. Log into the OBM console

    2. Create a new SNMP Policy: Administration > Monitoring > Policy Templates > SNMP Interceptor

    3. Give the policy a meaningful name.

    4. Click on the + sign and select "Event on matched rule".

    5. Add a display name (this is the condition name) and in the Event Object ID field, add .1.

    6. Save and deploy the policy to the node where the SAN is sending events.

    Then you'll start getting events assuming there is no firewall and the SAN is sending SNMP events to the right managed node.  

    How you would start managing your specific SAN really depends on your SAN and what features it offeres.

    I hope you get a better answer.

  • 0 in reply to   

    Dear Duncan,

    Thanks for the above information.

    I was  followed above steps and created the policy.

    I am getting SAN storage SNMP alerts to the BSM event browser.PF screenshot.

    Based on the alerts I was trying to create the meaning full events , but I am not getting these meaning full in event browser, still getting Unknown alerts even after creating the meaning full events.

    Can you please help me by using these alerts and OID's how I can create the meaning full events.

  • 0 in reply to   

    Dear Duncan,

    Thanks for the above information.

    I was  followed above steps and created the policy.

    I am getting SAN storage SNMP alerts to the BSM event browser.PF screenshot.

    Based on the alerts I was trying to create the meaning full events , but I am not getting these meaning full in event browser, still getting Unknown alerts even after creating the meaning full events.

    Can you please help me by using these alerts and OID's how I can create the meaning full events.

  • Suggested Answer

    0   in reply to 

    Hello there,

    I can't see yourscreen shot, but it's good if you have events in the console as that means events are arriving. People have their own ways of building policies, this is what I do:

    - For these newly arrived events, start looking at the "original message text" They will have different OIDs.  Sort the OIDs so they are unique.  Then take each one of these OIDs and start adding them as conditions to the policy:

    - Adding conditions is exactly the same as step 3 and 4 which is described above, but for step 5 add the OID you have in the console.  When adding the conditon, start filling in all the other fields within the condition.

     - There may be some events arriving that you don't want in the console, therefore add a "suppress" interval.  

    - To speed things up, you can copy the condition and change the OID along with some of the other fields like help text, severity and things like that.  You'll need to talk to your SAN administrator about those values.

    - For events that arrive all the time, change the condition order so these are matched first.  Also, add any suppress condition near the top of the condition order.  This helps the policy work efficiently.

    For more information please see https://docs.microfocus.com/doc/Operations_Bridge_Manager/24.2/OmucptSnmpInterceptorhtml and look at some another policy that's shipped with OBM as an example.

    That's really the best I can do.

  • 0 in reply to   

    Hi Duncan,

    Thank you so much for your reply.

    Screen shot attached for your information.

  • 0   in reply to 

    Hello there,

     

    Thanks for the screen shot.

     

    I’ve not tested your example, but matching this event would be something like this:

     

    Adding conditions for each OID, for example match:

    [1] .1.3.6.1.4.1139.103.1.18.1.1 <*.value1>

    [2] .1.3.6.1.4.1139.103.1.18.1.2 <*.value2>

    [3] .1.3.6.1.4.1139.103.1.18.1.1 <*.value3>

    [4] .1.3.6.1.4.1139.103.1.18.1.4 The used space on a file system <*filesystem> under the NAS server <*.NASserver> in the system <*.system> is over <#.ptcfull>% full.

    Pattern matching is based on https://docs.microfocus.com/doc/Operations_Bridge_Manager/2021.05/PatternMatchinghtml:

    This means the policy will match any event with these OIDs.  OIDs 1-3 you save the values (if you want them) as variables value1-3.  You can use these later in the event you send OR you can just match on .1.3.6.1.4.1139.103.1.18.1.4.

    This is how you can match the OID .1.3.6.1.4.1139.103.1.18.1.4 and create variables using your example:
    The used space on a file system nfs_ocpprod01_etcdbkp under the NAS server wat_uni-nfs in the system WAIT-UNI650F is over 75% full.

    Becomes:

    The used space on a file system <*.filesystem> under the NAS server <*.NASserver> in the system <*.system> is over <[#.pct] gt 70>% full.

    .1.3.6.1.4.1139.103.1.18.1.4 is a bit more interesting as it’s telling you the name of the filesystem, NAS server, system, and percentage full.  With this information, you can build up a message text where you use the variables, this looks like looks like:

    The used space on a file system <filesystem> under the NAS server <NASserver> in the system <system> is over <ptcl>% full. 

    The last part, <[#.pct] gt 75> means match the number (in this case 75) only if it’s greater than value 70 and save the number 70 as variable <pct>.  To get it working, try <#> first.  Please see https://docs.microfocus.com/doc/Operations_Bridge_Manager/2021.05/PatternMatchingDetailshtml for details. 

    Don’t forget, if you can, always fill in all the fields in the event attribute section as this helps identify CIs so OBM can do its magic. 

    Testing: I used NetSNMP snmptrap to build up test events – please google for examples.

    Sorry, but I can’t really do much more.  Please look at the shipped policy examples to see how to get pattern matching working.  If you need more help, please contact Opentext Professional Services.

    Best of luck.