Operations Bridge tips and tricks from your peers

Micro Focus Expert
Micro Focus Expert
1 0 795

ITOMinsiders.JPG

We presented a challenge to our ITOM Insiders group to offer some tips and tricks for Operations Bridge – Operations Manager (OM), Operations Manager i (OMi), Operations Manager UNIX (OMU) and Operations Manager Linux (OML). And here is what they offered.

The tips and tricks are organized by functions of Operations Bridge.

Events

  • Try to restrict unwanted (FYI) type events at the source to control the number of events and get most out of the consolidated event console. ITOM Insiders Member
  • The biggest strength of OpsB is the consolidation of events from various sources. For one customer, we were able to consolidate events from 25+ sources, most via Traps using BSM Connector. Once the head of IT Operations saw the value then the expectation was that all the other silo'd departments would work together to send the events to a central console. 

The next level of challenge is to filter the events & reduce the noise/event flood by suppressing unwanted alerts - for the NOC to effectively isolate the faults for faster Route Cause Analysis (RCA). Lastly, an effective events dashboard will make the biggest win-win for all departments within IT operations. Rakesh Kanojia

Migration

  • When you are moving from OML to OMi, make sure that your topology is up-to-date. You need to clean both the OML and NNM side to make sure to use the same names for servers/devices before you sync topology with OMi RTSM. ITOM Insiders Member
  • Did your NOC ask for Node Layout Group (Node Hierarchy) functionality? OMi is not similar to OML so you can use this workaround to replicate Node Hierarchy to OMi same as OML. You can create a top-level Node Group (NG) using the opr-node.sh utility into OMi. Then take a dump of node layout groups from OML and make a list and create the same NGs into OMi under top-level NG you created earlier. Then assign nodes to their respective NGs you just created. Then you can create an OMI view for these NGs you created. I would recommend creating some special unique identifier for these NGs you created e.g. description FOO. You can use this identifier to identify and include as a filter when you create the View. Mukesh Patel

Naming

  • Naming is absolutely paramount. Insure you are consistently using either the FQDN or the short hostnames, otherwise you will have your topology fall into disarray and the correlations out of the box will not work as expected. ITOM Insiders Member
  • If OpsBridge users want to see a full node name (with FQDN) in the OpsBridge console then you can achieve this by modifying the existing topology sync package on OMi to populate full node names instead of short names and then upload the package. You can do the same thing using EPI script but with the cost of performance. Mukesh Patel

Integration

  • When integrating OM and OMi servers, make sure that each OM or OMi server has exchanged certificates with all the other ones (through BBCTrustServer) to prevent Event Sync issues in the future.

And when using an AD account for the OM Connected Server setup in OMi, change the Role of the selected OM User directly in the OM database, from Operator to Administrator. This will give that OM all the rights it needs for the OM-OMi integration, preventing problems with Tool execution, for example. Raymond Meijer

  • OMi - NNMi integration Tip: If you have multiple NNMi servers and if you want to integrate them with OMi for topology sync then create a separate user for each NNMi e.g. us_nnm, eu_nnm, ap_nnm and use these users as integration users instead of using single default user for topology sync. You will get lots of benefits on OMi side for using separate integration users for each NNMi server. If you want to do something within OMi for per region this will be very helpful. You can create views to distinguish devices for each region and you can use these views for many things within OMi. E.g. to give access to users for a specific region, correlation rules etc. Mukesh Patel

UCMDB/RTSM 

  • Since RTSM within OMi is just UCMDB, and OMi 10.61 contains UCMDB 10.3x, you can simply copy the embedded UCMDB Browser 4.13 into the "odb/deploy" directory on your OMi GWs, and then restart these. Now you have to add the permission to use the widgets of UCMDB Browser widgets and then you are good to go without the need for admin rights, as you would need usually to use the RTSM Administration menu entry "IT Universe Manager". And it is even more readable (for most people, anyway). ITOM Insiders Member
  • The UCMDB/RTSM Web Services makes it easy to do some scripting where you can enrich CIs, create relations, and import/export. Carsten Abildgaard
  • For smaller OMi environments you can make use of the built-in Data Flow Management of RTSM (which is UCMDB). Which means, you can do discovery of your CIs directly from within OMi. Just be careful to use an exactly matching version of the Data Flow Probe! For bigger environments, I would recommend using an external/stand-alone UCMDB-Server to do the discovery and then replicate the CIs (and relations) of interest into OMi (RTSM).

Others

  • When using OMi 10.61, try to use HTML 5 components, some components using Flash can cause memory leaks.- Rok Ponikvar
  • NTP server should be the same for all devices - OMi servers and agents - Vladislav Saykov
  • When you go to the product home page of OMi you can download the OMi VA (Virtual Appliance). Which is simply a VMware VM containing a pre-setup OMi 10.61 (Deployment Guide included). ITOM Insiders Member

Thank you to Rakesh Kanojia, Mukesh Patel, Raymond Meijer, Carsten Abildgaard, Rok Ponikvar, Vladislav Saykov and a few others who know who they are for your contributions.

ITOM Insiders is an invitation-only community where you can complete activities to earn points towards exciting rewards, expand your network, and get recognized for being an amazing customer of Micro Focus - IT Operations Management (ITOM). To request an invite, go here.

Micro Focus Events

To get more information on this release and how customers are using Operations Bridge we are happy to announce the following events you can register for:

ITOM Customer Forum, Brussels – January 15, 2018 - link coming soon

ITOM Summit, Dallas, Texas – February 5-7, 2018 – link coming soon



Read all our news at the OpsBridge
blog

References

Explore all the capabilities of the Operations Bridge Suite and technology integrations by visiting these sites:

 

 

About the Author
Micro Focus Product Marketing. Over 20 years in network and systems management.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.