Infrastructure Management Software Blog

New SiteScope Adapter version 2.0

A guest post from Alfred Hermann, Operations Center Technical Marketing Manager.
- Peter


You probably know what the SiteScope Adapter is used for. Its purpose is to glue together HP SiteScope with HP Operations Manager to combine agent-based with agent-less monitoring. It offers the following capabilities:



  • You can forward SiteScope alerts into HP Operations Manager to manage from a single operations console.

  • The OM agent discovers SiteScope configuration and monitor groups, and publishes discovered information to the Operations Manager service maps.

  • You can launch SiteScope tools in-context from the OM console for further diagnostics of the environment.

  • Multiple SiteScope servers are supported (you have to install an OM agent on each SiteScope server).


In the first version of the adapter all alerts originating from SiteScope would relate to a single node in the OM Nodes / Node Group / Node Bank environment. Even though the alerts come from a variety of nodes monitored in an agent-less fashion, their status contribute only to a single element in the console.


This has changed with version 2 of the SiteScope adapter: SiteScope events can now explicitly be mapped to their respective nodes rather than consolidated altogether to the SiteScope server. The resulting value is obvious: The operator immediately notices where the problems are. No longer digging through some more event details…


In addition, interoperability with Operations Manager i  has been improved by setting a CI as resolution hint for OMi. Remember, OMi relates events to CIs in the UCMDB, and any resolution hint is mostly appreciated.


The new SiteScope Adapter 2.0 is available with HP Operations Manager version 8.16, alternatively as patch OMW_00039. For the UNIX based OM management servers you need OMU version 9.x. 


For HP Operations Center, Alfred Hermann.

Everything you wanted to know about OMi... (Q&A from Vivit technical webinar)

Thank you to everyone who attended the Vivit webinar. The recording is now available for viewing on Vivit’s web site. You can also download or view the presentation slides in PDF format. There were many questions from the audience. Jon Haworth and Dave Trout's answers appear below. I have grouped questions by topic.


Product Structure


















Are these 3 different modules to be purchased separately? (topology, event and service views) Yes three different modules. OMi Event Management Foundation is the base product and is a requirement before either of the other two products can be installed. OMi Health Perspective Views and OMi Topology Based Event Correlation are optional modules.
How is the licensing done? There are three separate OMi modules. OMi Event Management Foundation is the base product and is a requirement before either of the other two products can be installed. OMi Health Perspective Views and OMi Topology Based Event Correlation are optional modules. Each module is priced / licensed separately and the pricing model is 'flat' - you purchase the license(s) required and that is all (no CPU or tier or connection based pricing).
How does that scale to thousands of machines? Since we have just introduced OMi, we don't yet have a lot of "real" scalability data to report. However our internal testing so far indicates that OMi can handle the typical event rates handled by OMW/OMU in terms of forwarding events. Like OM today, the scalability of the total solution is not so much limited by how many thousands of machines are being managed but on the total event rate being handled.


Integration with Operations Manager, BAC, UCMDB














































Is there any description about the interface between OM and OMi. There are two interfaces used: 1) Message forwarding from OM to OMi, and 2) Web Services interface for message changes and Topology synchronization.
How is the integration with Operations Manager on Unix? As mentioned during the webinar, OMi requires either OMU or OMW as the event consolidation point for forwarding events into OMi. The event forwarding is configured in OM exactly the same way as if forwarding to another OM server. For message updates and topology synchronization, a Web Services interface is used.
Since it was mentioned it works with both OMU 9.0 and OMW 8.10, does it work with the mentioned SPIs on both platforms ? Yes. We are updating the SPIs to be "OMi ready". What this really means is that we're adding  a little extra information to the event messages (via Custom Message Attributes) to make it 'easier' for OMi to associate a message with the correct CI in the UCMDB and to include specific indicators needed for the TBEC rules in OMi. For OMU 9 we will release some updated SPIs soon which include enhanced discovery - very similar levels of discovery to what OMW has. The discovery subsystem is an area that we enhanced in OMU 9 and we want to be able to use the SPI discovery data as the 'starting point' for populating and maintaining CI and relationship information in the UCMDB - which is what helps to drive the logic in OMi.
How flexible are the integration with BAC products? Are these factory built and need factory to modify due to target environment requirement OMi and BAC use the same UCMDB instance so they are tightly integrated 'out of the box'. OMi is completely built on top of the BAC platform technology. It supports the same security mechanisms, the same HA configuration options, the same user/group definitions, etc. In short, OMi is just like any other BAC "application" that is leveraging the platform.
In the installation guide, it says that one of the requirements is to install the "BSM platform". What exactly do you understand on "BSM platform"? BSM platform means "BAC". OMi 8.10 requires BAC 8.02 as the BSM platform.
Can you run OMi without BSM? No, the BSM platform provides the user interface 'framework' and the runtime UCMDB. OMi plugs into the BSM foundation.
Which security model will take precedence - OMU responsibility matrix or the BAC security for views? OMi security is entirely based on the BAC platform features. Access to OMi views, admin UIs, etc. is all controlled through the standard BAC security features (users/groups, roles, permissions, etc.)
Which security model will take precedence - OMU responsibility matrix or the BAC security for views? OMi security is entirely based on the BAC platform features. Access to OMi views, admin UIs, etc. is all controlled through the standard BAC security features (users/groups, roles, permissions, etc.)
What is the price policy if you have / have not BAC already installed? Having BAC installed makes no difference to the price. OMi includes all components needed (runtime UCMDB etc.) in the license. Pricing is based on a 'flat' price for each of the three modules (see earlier question). You need to contact your local HP sales representative to obtain local pricing.
CI treeview scale? The CI Tree view is basically a UCMDB VIEW/TQL under the covers. TQLs in UCMDB are tuned for VERY efficient retrieval of CI information.


Integration with Ticketing Systems (Service Manager, Service Center)






















How does OMi interact with any ticketing system like Service Manager or Service Center. Will the Ci's health be reflected based on ticket info? In this first release of OMi, there is no direct interaction with a ticketing system. The interaction is driven through the existing OM (OMW or OMU) to Service Manager / Service Center interface. Because OMi synchronizes message changes back to the OM server that it is connected to, trouble tickets can be triggered from that OM server.
How does this interface to Service Manager 7? The interface to SM 7 is driven through the existing OM (OMW or OMU) interface to Service Manager. Because OMi synchronizes message changes back to the OM server that it is connected to, trouble tickets can be triggered from that OM server.
The slides implied "assignment" which looked similar to NNMi. How do the new features of OMi integrate to Service Manager? The concept of assignment is 'internal' to OMi. In many organizations the tier 1 support personnel will deal with non Business Service impacting issues without raising a trouble ticket. NOTE: this is purely dependent on the individual process and organization structure that is selected, we know that a lot of companies work this way to minimize the number of TTs. Some organizations insist that every actionable 'incident' becomes a TT. Where an event is dealt with in OMi then assignment makes sense, where events are forwarded to SM7 or another TT system then assignment will likely take place in the Incident / Helpdesk system.
Will OMi integrate with ITSM (change management app from Front Range)?  Also, I'm assuming that we will need to purchase CMDB for event correlation regardless - is that true?  Cannot comment on the Front Range application. It is likely that an integration may be possible but it would be wise to verify with the vendor what external interfaces they provide for integrating event management systems with their product. No you do not need to purchase UCMDB - we provide a 'free' runtime with OMi.


UCMDB, Discovery and Smart Plug-Ins (SPIs)


































Is it necessary to have UCMDB to have OMi? OMi ships with a "BAC 8.02" media kit. This actually provides the BSM PLatform - including UCMDB - and is licensed using your OMi license key. If you do not have an existing UCMDB then this will provide a runtime UCMDB as part of the OMi product package. If you have an existing BAC 8.02 installed (which includes UCMDB) then you can utilize that for OMi.
Is discovery best done in OMi or uCMDB? All discovery data is maintained in the UCMDB. The 'base' discovery for OMi will be provided by the Smart PlugIns that have been deployed from the OMW or OMU instance that OMi is connected to. Additional discovery data can be added to the UCMDB - for example from NNMi or DDM - and OMi will make use of this discovery data if it exists.
If using DDM for discovery, DDM-Advanced is recommended since it can discover not only hosts but also applications and their relationships.
Can you please tell me if DDMi can be used as a feed? Yes. Servers discovered by DDMi are inserted into UCMDB. However be aware that DDMi does not discover applications and dependencies/relationships. DDM-Advanced is the recommended discovery approach if you plan to use OMi and leverage the TBEC rules in particular.
If uCMDB already has CIs populates by DDM, would the new sources like NNMi , SPIs conflict with them , in other words do we need a clean uCMDB ? No. A clean UCMDB is not required. OMi is designed to work with CIs reqardless of how they are discovered and inserted into the UCMDB. In general, reconciliation of CIs discovered from multiple sources is handled automatically.
Can you clarify what you mean by "we are including these SPIs"? Does this mean it's part of the shrink wrap deliverable with OMi?  What specifically will the virtualization SPI provide?  We were considering another product for that space, but want to hear more about those capabilities. We are not including SPIs with OMi. We are including pre-defined content (event type indicator mappings, health indicators, TBEC correlation rules) for the SPIs that we noted. If you have these SPIs deployed then the time to value when OMi is deployed will be very quick. HP released a SPI for Virtualized Infrastructure monitoring earlier this year. Initial focus is on VMware but we will be providing an update soon with more features. You can contact your HP Software Sales Representative to get more details of the specific functionality provided.
 What is the virtualization SPI? Is it nWorks SPI ? No. HP released the Smart PlugIn for Virtualized Infrastructure early in 2009. This is a HP developed and marketed product.
nWorks is the "SPI" we were considering This is a different SPI and is based on a different architecture (agentless polling). It has no OMi content at present and it will be the responsibility of Nworks / Veeam to provide this.


KPIs (Key Performance Indicators)


















What is a KPI? KPI - means Key Performance Indicators
where do you define the KPIs? OMi provides four KPIs to the BAC platform: Operations Performance, Operations Availability, Unresolved Events, Unassigned Events. These are defined by OMi, not by users. What IS configurable is which Health Indicators (HIs) are assigned to impact either the Operations Performance or Operations Availability KPI for specific CI Types. This is done using the Indicator Manager in OMi.
If the difference is KPI, why data is not collected from PM. Instead I see that the data is collected from OVPA & OV agents. OMi is focused around event processing. Events (alerts) are 'collected' from OVPA and OV agents to enable operations staff to understand what needs to be 'fixed'. PM (Performance Manager) is one tool that can be used to assist in the analysis / diagnosis of performance problems. PM is actually integrated into the OMi user interface.


Topology-Based Event Correlation (TBEC)


























In the slide with "Carol" and "Bill", they applied their knowledge to (I guess) develop some rules?  Is that work that still has to be done manually?  What were they developing - KPIs? No not KPIs. The example is there to show how TBEC rules are simple to create but that the correlation engine 'chains' them together to provide quite complex correlations logic which adapts based on the topology that has been discovered. We (HP) are providing content (Event Type Indicators, Health Indicators, TBEC rules as per "Carol and Bill") for a number of our existing Operations Manager Smart PlugIns with OMi and we will continue to add additional content moving forwards. The example in the slide is there to illustrate the process (simple process) of creating very powerful correlation rules which adapt to changes in the discovered infrastructure. You would only need to undertake this process where HP does not provide out of the box content with OMi.
I have some questions regarding the TBEC, is there any experience regarding the performance?
How many events can be handled by the correlation engine per sec?
The engine is tuned for very high performance. It is basically the same engine that is used in NNMi for correlations.
With topology synchronization with NNMi do you have to have OMi licenses for every node in NNMi as well? ... I.E. if you are using Topology Synchronization with NNMi will it only show the nodes from NNMi that have OMi agents installed? No. All CIs in the UCMDB are visible to OMi. No additional license costs are required for NNMi nodes which are added to the UCMDB.
Which language is used for the correlation rules? And where are the rules defined ? (UCMDB?) TBEC is configured in the OMi Correlation Manager GUI, there is no programming language involved. The rules are based on topology (a View from the UCMDB) and on specific Health Indicators with specific HI values.
Does OMi support the execution of validation routines when closing an Alert/Event that also closes other related items? Not currently out of the box. There are several configurable settings which affect TBEC behavior (e.g. correlation time window, automatic extension of time windows, etc.), but currently this is not one of them. We are considering additional options for the future.


OMi Features


























Scalability, High Availability Cluster Support?  Estimated max seats before going distributed? OMi supports the same cluster/HA features as supported by BAC. For example, you can have multiple gateway servers connected to a clustered Data Processing Server and a remote database server. In this case, OMi software is installed on each of these separate servers (gateways and DPS). In general, the "max seats before going distributed" (i.e. adding gateway servers) would be driven by the same considerations as documented for BAC itself. More information specific to OMi environments will be available over time as we have a chance to do further testing and characterization.
Does OMi have a reports generator showing things like daily TBEC, etc.? Not currently. However the BAC reports (e.g. KPIs over Time) can be used to look at how the OMi KPIs are changing over time on CIs.
Comment: We feel that most of these features being discussed in OMi should have been as an upgrade to OMW. Too many modules to buy and try to integrate ourselves. For example we wanted a better version of the OVOWeb to come as an upgrade in OMW8.1. Too many products to buy just to manage our network. OMi is providing discreet and incremental value above and beyond what is provided in OMW or OMU. We are continuing to enhance both OMW and OMU (for example the recent release of OMU 9.0) and customers who are happy with the capabilities of these platforms can continue to move forwards and take advantage of the enhancements that we are providing. There is no requirement to move to OMi.
We feel we are being charged for features that were supposed to be in products that we already purchased. We are not happy about the tactic of releasing new products to fix features that were advertised in prior software. As a consultant, even I get lost in the vast amount of monitoring tools being sold by HP. OMi  is providing discreet and incremental value above and beyond what is provided in OMW or OMU. This functionality was never offered as part of OMW or OMU - it is new and unique to OMi. The reality is that it would have been extremely difficult, and time consuming (slow to release) to provide the high value capabilities of OMi within OMW or OMU. The strategy we have choosen is to base these new capabilities on a 'clean' build based on contemporary technologies - but HP has specifically ensured that existing OM customers who wish to take advantage of these new capabilities can do so without having to disrupt their existing OM installation.
I had some issue when trying to setup and run the synchronization tool and event forwarding. Who can I contact? You should contact your normal HP support channel for assistance.


Other














Is there an estimated time line for detailed technical training on OMi? We have just run a series of virtual instructor led training sessions for our partners. HP Education Services will be releasing an OMi class in the near future.
Where can I get an evaluation version of OMi? You can request a DVD from the trial software web site. A download will be available at http://www.hp.com/go/omi soon.


 


 For HP Operations Center, Peter Spielvogel.


Get the latest updates on our Twitter feed @HPITOps http://twitter.com/HPITOps


Join the HP OpenView & Operations Management group onLinkedIn.



 

VMware: the Next Infrastructure Management Behemoth?

I read an interesting blog post on virtualization.info that discussed how “VMware is becoming an infrastructure management company.” It walks through all their recent acquisitions and how these may point to a long-term goal of a much larger market presence. This, combined with overall market trends (a customer I spoke to yesterday said their goal is 90%+ virtualization) could lead them to a very different position (mainstream rather than niche) in the infrastructure management market.


Our approach to virtualization is to treat virtual servers the same as physical ones. Our customers can use the exact same instrumentation to monitor the performance and availability of virtual and physical servers. HP’s infrastructure management software can manage any hypervisor (VMware, Microsoft, Citrix, etc.), any brand of hardware (HP and our competitors), and every major business application. Our customers can perform problem isolation and diagnostics across all these elements, which we tie together using a universal configuration management database (UCMDB).


We’ll see where all this goes. We certainly live in interesting times. What do you think VMware is up to?


For Operations Center, Peter Spielvogel



 

Making the Best Use of the Tools You Have

I spent the day today at our executive briefing center with a customer that provides online spend management services. They have a number of our data center products, so we spent most of the day discussing integration. The agenda was simple. They wanted to learn how to:




  1. Make the best use of the tools they have


  2. Determine where they should be looking next

First, let’s examine their environment, which in turn drives their requirements.


Hardware
They have a variety of hardware, some HP servers and storage and some from other vendors. Some of this hardware is at the end of its lifecycle and in line for replacement. They want to dramatically reduce their power consumption with the replacement servers. Part of the savings will come from consolidation onto fewer, more powerful machines; part from newer hardware that is more energy efficient. We did not discuss replacement hardware explicitly today, but one topic of concern was that their current infrastructure management software must have the flexibility to manage future hardware purchases.


Virtualization
They are very interested in moving aggressively towards virtualizing most of their IT infrastructure. They want to be able to manage both physical and virtual servers and storage using a single set of instrumentation.


Software
Service Desk. They are using most of the modules within HP Service Manager. This allows them to manage their help desk efficiently and track changes throughout the enterprise.
Configuration Management Database. They have HP’s uCMDB (“u” for universal), which manages all the configuration items (CI) within their enterprise. In an effort to streamline their operations, they also purchased our Discovery and Dependency Mapping (DDM) software to automatically discover their IT infrastructure and populate the CMDB. The CMDB is the foundation layer that ties together all the components within our Business Technology Optimization suite. In addition to maintaining state and configuration information about individual CIs, it understands relationships among them, and how these align with business services.
Network Management. They use an open source network management software.
End-User Monitoring. They use a commercial product (non-HP). They purchased it last year to replace home-grown scripts. It runs synthetic scripts (similar to our End User Management software)
Operations Manager. They just purchased Operations Manager, along with agents, but have not yet deployed it. The prospect of consolidating several existing management consoles was one of the main reasons driving the purchase.


Presenting a Complete View of the IT Infrastructure
We started with the usual slide presentations that showed all the nice relationships among the products. Of course, heads nodded in agreement when we mentioned self-inflicted IT problems, the finger-pointing among groups during troubleshooting, and the challenge of seeing everything through a single console.


The key problem emerged that they lack a holistic view of the entire environment. Fortunately, once they deploy Operations Manager, this will solve the problem. It provides a “single pane of glass” in which they can view events from across their entire infrastructure, including the non-HP servers, non-HP network management, and non-HP user monitoring, in addition to all their HP hardware.


Generate (Enriched) Service Tickets from Events
And, Operations Manager can automatically open tickets in Service Manager. In addition to opening tickets based on events, Operations Manager enriches the events with all the relevant information from the CMDB including the affected business service. Once the incident is closed, either manually or automatically, Operations Manager will clear the event in its console and then tell Service Manager to close the ticket .That wrapped up the section on making the most of what they already have.


Automation Cuts Costs
Then, things got really interesting when we went to the white board. We outlined how much money they can save by implementing Operations Orchestration, our runbook automation solution, to automate some of the routine actions an operator would perform using Operations Manager. We used an example of another customer who saved $400K per year just by automating a database fix that takes only one minute to fix. That problem occurs 400 thousand times per year. At $1 per minute for support costs, do the math.


This paints a clear picture of where they should be looking next. And, all the discussions were based on released technology that is available to anyone today.


Let us know how you are making the best use of the tools you have. We’ll give you some expert guidance about what steps to take next that will further increase the return on your investment in infrastructure management software.


For Operations Center, Peter Spielvogel.

Search
Showing results for 
Search instead for 
Do you mean 
Follow Us


HP Blog

HP Software Solutions Blog

Labels
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation