Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
What's new in OMi MP for Infrastructure 2.00
Following are enhancements available in OMi MP for Infrastructure 2.00.
OMi MP for Infrastructure 2.00 monitors the Amazon Web Services on Linux platform.
Enhancements in System Infrastructure Monitoring
Process Monitoring
Monitoring all the required process and process groups only on UNIX platform. Sys_ProcessMonitor and Sys_ProcessMonitorConfig policies are added to Key System Services Availability Aspect. You must specify all the process and process groups in Sys_ProcessMonitorConfig policy before deploying the Aspect.
Adaptive Threshold
The adaptive threshold concept is used to determine optimal threshold values by using the historical records for performance characteristics and usage patterns of infrastructure resources, instead of using fixed threshold values specified in the policies. The policies that use adaptive thresholds calculate the average value of the metric during the last hour. The average value is then compared to the data collected in the previous four weeks during the same hour or day interval. If there is a significant difference in the value, the policy generates an alert.
Constant threshold values set in the policies are ideal for a specific scenario, but not for all scenarios. It is necessary to change the threshold values according to the type of environment for improved performance of the infrastructure resources. Distributed system environments generally follow predictable trends over time. Adaptive threshold helps to automatically calculate the threshold values according to available performance data for previous weeks.
When policies that use adaptive threshold are deployed on managed nodes, the adaptive threshold script establishes a baseline from the historic samples. The policy stores the value of the metric collected from the previous 4 weeks for the same day and same time slot known as Historic Data or Baseline Data. The sampled data is collected from the Embedded Performance Component or Performance Agent. These samples help identify previous trends in infrastructure performance. Based on these trends, the threshold range is automatically calculated.
Configuration Change Monitoring
The CCI Monitor policy monitors files, Windows registry settings, and command output for changes. All configuration changes that you monitor are added to the Config File policy or to the configuration file ccilist.cfg located at:
On Windows
%OvDataDir%\conf\ccimon\configuration
On UNIX
var/opt/OV/conf/ccimon/configuration
The CCI Monitor policy reads the ccilist.cfg file at every run and sends alerts when there is a change in files, Windows registry settings, and command outputs.
Desired State Monitoring
Desired State Monitoring monitors files, windows registry settings, and command outputs in the ccilist.cfg configuration file.
After deployment, the Desired State Monitoring checks for == in the ccilist.cfg configuration file and compares the files, windows registry settings, and command outputs added in the configuration file with the corresponding reference or gold file. Alerts are generated whenever there is a change in the monitored file, windows registry settings, and command outputs.
Real time alert
The RealTimeAlerts policy monitors the bottlenecks in CPU, disk, memory, and networking. The Realtime Configuration policy defines the threshold for these parameters. During a threshold breach, alert messages notify the system administrator with no time delay and reduce the downtime in the production environment.
Note You must enable RTMA license on the Operations Agent node for RealTimeAlerts policy to fetch real time data.
Security policies for Log File Monitoring
- Enhanced monitoring of bad logins and system log for AIX, HPUX, Solaris, and Linux.
- Enabled login monitoring for AIX, HPUX, Linux, and Solaris.
- Enabled monitoring of SNMP logs for Solaris.
Energy Data Collection
The Start/Stop Collection is a tool used to collect metrics from systems where Operations Agent version 12.x is running. This tool measures the energy utilization of physical machines where multiple virtual machines are installed. The Start/Stop Collection tool is supported only on Windows and Linux platforms and functions only when Integrated Lights-Out (iLO) is installed on the physical server.
Operations Agent Self Monitoring
Agent policies are included to monitor action agent, external monitor, SNMP traps interceptor, critical Operations Agent processes, message interceptor, and log file encapsulator.
Performance Collection Component
Aspect containing policies to centrally manage the Operation Agents' parm, alarmdef and hpsensor config files, along with a corresponding message interceptor policy, for AIX, HP-UX, Solaris, Linux, and Windows.
Log File Monitoring
System Log Collection Aspect contains the policies to collect and forward for system log file only on Linux. Log data is collected from syslog.conf for OS version earlier to RHEL 6 and from rsyslog.conf for OS version RHEL 6 or later. Monitoring the log data from boot.log file is not support in this version. Analytics tools such as Operations Bridge Analytics can use these logs to predict the trends and identify the issues in your IT environment. The aspect and policies are available in OMi_MP_for_Infrastructure_LogStreaming_AddOn_02.10.000, which can be imported additionally before or after installing the OMi MP for Infrastructure 2.00.000 version. The log streaming is available only for OMi version 10.61 or later and is supported only from Operations Agent 12.03 or later. You must configure the forwarding policy to specify the target.
Related Topic
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to docfeedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: