on the adapter in proportion to the number of events discarded by the NNM circuit settings and therefore not forwarded to the adapter. If you are running NNM 5 or earlier, the adapter calls OVsnmpTrapOpen to open a session; with NNM 6 or later, the adapter calls OVsnmpEventOpen. Only OVsnmpEventOpen allows for event correlation of the events before they are forwarded to the adapter.

OVsnmpEventOpen contains a filter parameter that defines which events the application receives from ovspmd. A filter value of NULL or the empty string (“”) prevents the adapter from receiving any events and makes the session a send-only session; therefore, this is not a recommended configuration. See the manual page for OVsnmpEventOpen for more information.

The configuration file keyword HPOVFilter passes the filter value you specify to OVsnmpEventOpen. HPOVFilter specifies what kind of events are forwarded to the adapter from ovspmd and contains the value that will be used for the filter parameter when calling the OVsnmpEventOpen API. If you have NNM 6 and HPOVFilter is not specified or is commented out, the adapter receives all events by default. For more information about HPOVFilter, see “Configuration File” on page 70.

Determining the OVsnmpEventOpen Filter Value

The following examples show two ways to see how the value in HPOVFilter is passed to OVsnmpEventOpen.

vExample 1: NNM input event tracing is turned on and adapter tracing is turned off.

Look in the file $OV_LOG/ecs/<ecs-instance#>/ecsin.evt#and do a find on previous tecad_hpov from the bottom of the file. The following example is similar to what you can see (the filter in this example is {CORR{default}} .*):

Trap-PDU {

enterprise {1 3 6 1 4 1 11 2 17 1}, agent-addr internet : "\x92T$\057", generic-trap 6,

specific-trap 59179056, time-stamp 0, variable-bindings {

{

name {1 3 6 1 4 1 11 2 17 2 1 0}, value simple : number : 14

},

{

 

 

 

 

name {1 3 6

1 4 1 11 2 17

2

7

0},

value simple : string : \

 

 

"{CORR{default}} .*"

},

 

 

 

 

{

 

 

 

 

name {1 3 6

1 4 1 11 2 17

2

9

0},

value application-wide : address : internet : "\x92T$\057"

},

{

name {1 3 6 1 4 1 11 2 17 2 8 0}, value simple : string : "tecad_hpov"

},

{

name {1 3 6 1 4 1 11 2 17 2 10 0}, value simple : number : 14128

}

}

}

% ber:Trap-PDU:

Chapter 5. OpenView Adapter 67

Page 78 Page 80
Page 79
Image 79
IBM Enterprise Console manual Determining the OVsnmpEventOpen Filter Value
Page 78 Page 80

Enterprise Console specifications

IBM Enterprise Console is a robust solution designed to centralize and streamline IT operational monitoring and management. As organizations increasingly rely on complex IT infrastructures, including cloud services, on-premise systems, and hybrid environments, the need for an effective monitoring tool has become paramount. IBM Enterprise Console addresses these needs by providing a comprehensive view of IT operations, enabling organizations to respond to incidents with agility and precision.

One of the key features of IBM Enterprise Console is real-time monitoring. The solution offers a single pane of glass through which IT teams can observe the performance of various systems and applications. This capability allows organizations to detect and respond to incidents promptly, minimizing downtime and ensuring that services remain available for end users. The console integrates seamlessly with multiple data sources, allowing for the aggregation of alerts, events, and logs from diverse IT environments.

Another significant aspect of IBM Enterprise Console is its automation capabilities. The platform supports automated workflows and incident management processes, helping to reduce the workload on IT teams. Automation not only enhances efficiency but also ensures consistency in incident response. By leveraging predefined rules and actions, organizations can standardize their operational protocols, leading to faster resolution times and improved service quality.

The IBM Enterprise Console utilizes advanced analytics and artificial intelligence to enhance operational insights. Machine learning algorithms can help identify patterns and anomalies in system performance, allowing organizations to anticipate potential issues before they escalate into critical incidents. This proactive approach to IT monitoring not only improves reliability but also fosters a culture of continuous improvement across the organization.

Security features are also integrated into the IBM Enterprise Console, allowing for the monitoring of security incidents alongside IT operations. This unified approach helps organizations to respond more effectively to security threats, enabling them to correlate operational and security data for a comprehensive view of their infrastructure.

In conclusion, IBM Enterprise Console stands out as a powerful tool for IT operations management. Its real-time monitoring, automation capabilities, advanced analytics, and integrated security features make it an ideal solution for organizations looking to enhance operational efficiency and responsiveness. By leveraging this technology, businesses can ensure that their IT environments remain stable, secure, and aligned with their strategic goals.
Top Page Image Contents