For example, in the HP BSM solution, when HP Application Performance Management (APM) and NNMi are both integrated with the BSM console operators can quickly identify a fault in the network hosting the application where APM has found a problem. This integration paints a consolidated picture of integrated application downtime caused by network failures even though the application is hosted on heterogeneous domains shown in the BSM dashboard.
This post describes several use cases for NNMi integrated with BSM.
Use case #1: NNMi topology in the BSM console for network and applications:
Consolidating all network entities into the BSM console provides a single pane of glass for troubleshooting problems. Logical components such as subnets, VLANS, interfaces, addresses, and physical components such as cards, ports, and connections are synchronized from NNMi to the BSM console. These synchronized network entities are now uniquely identified by the BSM console with a unique identification scheme, called Configuration Items (aka CI’s) which are modelled using a common repository called the HP Universal Configuration Management Database (uCMDB). These CI’s can be used by any BSM persona to build a model comprised of business services, applications, databases, and storage which are linked to these network entities.
These CI’s can also be used to raise tickets during network issues for the network admin to resolve. Now that the operator knows the connection between a network element and the applications it supports she can prioritize specific network faults based on business impact and can improve mean-time-to-repair for business-critical applications. Without this connection the ticket becomes one of many that are handled in sequential order without concern to high priority versus low priority applications.
The following diagram illustrates various network entities that are synchronized from NNMi to the BSM console. Various personas can build service layers, application layers, and network layers based on these.
Below are a set of diagrams that illustrate various topological relationships of NNMi entities after they are forwared to BSM, as seen in the BSM console.
Figure 1: “Network Topology” The view in the BSM console illustrating the relationship between the IpSubnets, nodes and IpAddresses. Node(s) containing IpAddress(es) is a member of IpSubnet(s)
Figure 2: “VLAN Nodes by NNM” The view in the BSM console illustrating the relationship between Vlans, its Physical ports and Nodes.
Figure 3: “Layer 2 by NNMi” The view in the BSM console illustrating the relationship between L2Connections, Nodes and Interfaces.
Use case #2: BSM user wants to take corrective action from the consolidated picture of NNMi events in the BSM console:
NNMi generates events (aka incidents) for the SNMP traps resulting from network faults. NNMi has a family of Smart Plugins (SPIs) for a number of network monitoring situations that also generate events through NNMi. These incidents can be viewed in the Event browser of HP OMi (part of the BSM console). You can now get a consolidated Event Management dashboard view allowing you to prioritize any given event compared to other issues in the infrastructure.
The NNMi management server forwards incidents to the BSM event console using adapters.
In the BSM console, an operations person can analyze these NNMi forwarded events and perform the following:
Assign the incidents to various users and groups based on roles
Forward these incidents to a ticketing solution like HP Service Manager (HP SM)
Take automatic actions in the form of policies for pre-defined conditions
Change the life cycle state of the incidents based on actions taken
Launch the NNMi console for viewing the performance graphs, L2/L3 topology maps, server and nodes status, etc.
Categorize all related events starting from an application all the way to the Infrastructure element.
Figure 4: Illustrates the NNMi incident as seen on a BSM console as an event with the details such as Severity, State, Related entity, Event Type Indicator (ETI) and the type.
Use case #3: BSM console user wants to launch NNMi reports:
The MyBSM dashboard can bring up views from NNMi giving an integrated picture of a network element (node) and corresponding dashboard of its related data like L2 neighbor view, L3 neighbor view, incidents, and overall network health. This gives a complete picture of a network element in relation to the rest of the infrastructure, thereby determining if the problem is a network fault affecting the application or not. And, if it is a network fault, determining the cause.
Figure 5: Illustrates the customized MyBSM dashboard in the BSM console. A node selection depicts its L3 Neighbor view, a path view to any connected neighbor and the open incidents related to the node.
The goal of the BSM solution is to provide a complete view and troubleshooting environment for the IT infrastructure. Each of the components in the BSM suite contributes to that view, making what was previously unknown, now known. In this post we’ve shown how NNMi brings network information and events into the BSM console and helps level one operators be more effective.
The whole BSM solution including network management will be on display at HP Discover June 2-4 in Las Vegas. Stop by to get a demonstration, ask questions or just say hello. Uncover the unknown.
About the authors:
Waheeda Anjum has nine years of experience in software testing with multiple domain experience in HP BSM Portfolio. In the network management portfolio she has worked on HP NNMi and HP NA products. She is responsible for testing the core NNMi and its integrations with other products for quality assurance.
Anjum has a Bachelor of Engineering (B.E) degree in Electronics and Communication from Anna University, India.
Madhusudhan V has been with HP software for close to 10 years handling multiple products across Systems and Networks domain, in the testing arena. He is currently part of NNMi System test team.
- Michael Procopio LinkedIn.com/in/Michael Procopio