Documentation. This PDF was generated for your convenience. For the latest documentation, always see

Transcription

1

2 Management Pack for Infra 2.00

3 Table of Contents Home... 1 Release notes... 3 What's in new OMi MP for Infrastructure Known issues, limitations and workarounds... 6 Deprecations Get started Key concept Install Prerequisites OMi MP for Infrastructure Package Install OMi MP for Infrastructure version Import OMi MP for Infrastructure AddOn Verify OMi MP for Infrastructure 2.00 Installation Configure OMi MP For Infrastructure Upgrade Administer Customizing Infrastructure Management Templates Creating Infrastructure Management Templates Editing Infrastructure Management Templates Configure Adaptive Thresholding Aspect Configure Change Configuration Monitor Aspect Configure Key System Service Availability Aspect Configure Realtime Resource Bottleneck Aspect Configure Streaming of Logs Configure Structured Log Streaming Policy Configure Data Forwarding policy Use Set up Infrastructure Management Templates Essential Cluster Management Template Essential IBM Power Management Template Essential Oracle Solaris Management Template Essential System Management Template Extensive IBM Power Management Template Extensive Oracle Solaris Management Template Extensive System Management Template Set up Infrastructure Aspects Systems Infrastructure Aspects Virtualization Infrastructure Aspects Cluster Infrastructure Aspects Parameters Tuning of Parameters Configuration Items and Configuration Item Types Run Time Service Model (RTSM) Views Event Type Indicators (ETIs) Health Indicators (HIs) Topology Based Event Correlation (TBEC) Rules Mapping Rules Operations Orchestration (OO) Flows Tools Performance Dashboard and Graph Templates Troubleshoot General troubleshooting Download PDF This PDF was generated for your convenience. For the latest documentation, always see

4 This PDF was generated for your convenience. For the latest documentation, always see

5 Home CustomerInformationPortal Release notes Get an insight of the latest features and everything that is new in this version. Get started Initiate your understanding of the key concepts of MP for Infrastructure. Install Use these procedures to install, set up, and configure MP for Infrastructure. Upgrade Use these procedures to upgrade from previous versions to current version. Administer Use this section to administer streaming of metrics and logs for MP for Infrastructure. Use Utilize the procedures to optimize the potential use of MP for Infrastructure.

6 Troubleshoot Resolve problems you might encounter while using MP for Infrastructure.

7 Release notes CustomerInformationPortal This section provides information about the new features, known issues, limitations, and depreciations of OMi MP for Infrastructure. What's in new OMi MP for Infrastructure 2.00 Known issues, limitations and workarounds Deprecations

8 What's in new OMi MP for Infrastructure 2.00 CustomerInformationPortal Following are enhancements available in OMi MP for Infrastructure 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

9 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_ , which can be imported additionally before or after installing the OMi MP for Infrastructure version. The log streaming is available only for OMi version or later and is supported only from Operations Agent or later. You must configure the forwarding policy to specify the target. Related Topic Configure Streaming of Logs Importing Content Pack for Infrastructure AddOn Use

10 Known issues, limitations and workarounds CustomerInformationPortal The known problems and workarounds for OMi MP for Infrastructure 2.00 are as follows: ID Issue

11 Infra MP [Doc] WorkAround for System Infrastructure Discovery fails on Ubuntu Node needs to be captured in Release Notes. Workaround: To resolve this problem, apply CIs related to the corresponding node and follow these steps on the BSM Server: 1. Create a folder named Linux_Deb on the BSM Server at the following locations.for Linux:/var/opt/OV/shared/server/tmp/deployment/instrumentation/SystemsInfrastructure/Unix For Windows: %OvDataDir%\shared\server\tmp\deployment\instrumentation\SystemsInfrastructure\UnixIf the above folder is not available on the BSM Server, then first deploy System Infrastructure Discovery on any non- Debian node and proceed with the steps. 2. Copy GetLogfileName.sh and ispi-ovperl files from the /var/opt/ov/shared/server/tmp/deployment/instrumentation/systemsinfrastructure/unix/linux folder into the Linux_Deb folder:for Linux:cp Linux/* Linux_Deb/For Windows:copy Linux\* Linux_Deb\ 3. Deploy the System Infrastructure Discovery Aspect on the node. 4. Verify if the files are present at the following location on the node:/var/opt/ov/bin/instrumentationon successful run of System Infrastructure Discovery, all the CIs related to the corresponding node will appear in Runtime Service Model (RTSM). QCCR8D39135

12 QCCR8D54256 QCCR1H90348 Agent Self Monitoring policies facing issues under OMi MP for Infrastructure2.00. Workaround: Missing file in the instrumentation folder and process running for older policies. Agent self monitoring is supported only on versions ealier to Operations Agent It is recommended to use Operation Agent Health View for self monitoring of Operaitons Agent from or higher versions. To perform self-monitoring for Operations Agent 11.x version, perform following: 1. Instal the HOTFIX_OMI_MANAGEMENT_PACK_FOR_INFRASTRUCTURE_QCCR8D _06_20 hotfix. 2. Deploy the Operations Agent Self Monitoring Aspect to the node. The CIs discovered by Virtual Infrastructure Discovery are not populated by IBM HMC toposync. Workaround: You must add the product name as ibm_power_hypervisor in the enumeration product_name_enum. To add the product name, follow these steps: 1. Click Admin > RTSM Administration > CI Type Manager > CI Types > System Type Manager. The System Type Manager dialog box appears. 2. Double-click product_name_enum and click Apply. The Update List Definition appears. 3. Add ibm_power_hypervisor to the list and click OK. You are not able to differentiate between the FileSystem Configuration Item (CI) type when multiple, similar nodes, or FileSystems are discovered. Workaround: To distinguish the FileSystem CIs for multiple nodes, follow these steps: 1. Click Admin > RTSM Administration > Modeling > CI Type Manager. 2. In the CI Type Manager window, from the CI Types pane, click Managed Object > Configuration Item > QCCR1A Infrastructure Element > Node Element > FileSystem. 3. In the right pane, click Default Label tab. 4. In the CI Type Label Definition format, add user_label to mount_point root_class.for example, user_label mount_point root_class 5. Click Save. QCCR8D38632 End users cannot setup KVM monitoring due to missing documentation. QCCR8D51142 Assignment deletion does not remove the policies on Operations Agent node which has policies deployed from OMi with OMi MP for Infrastructure version prior to QCCR8D49171 FileSystem Monitor set Application Attribute to DHCP. QCCR8D50872 Mounted CDROM generates Major event. QCCR8D50871 MP for Infra, service discovery, back slash is deleted from mount point folder path. QCCR8D49163 File System Space utilization monitors wrong devices, generating false alarms. QCCR8D46191 Fix the initialization and vbscript failures coming from the Extensive System Management Template. QCCR8D44434 Performance Alert Utilization alert showing repeating alert conditions. QCCR8D43248 Sys_LinuxKernelLog 1.0 generates too many events for the same issue - message key to be tuned. QCCR8D38633 Cannot graph KVM VM metrics using the VM node CI as context.

13

14 Deprecations CustomerInformationPortal Updates in Virtual Infrastructure Monitoring X86 Virtualization Technology Evolution OMi MP for Infrastructure 2.00 will not support monitoring of X86 Virtualization. It is recommended to use monitoring only edition of Cloud Optimizer for monitoring x86 Virtualization technologies such as VMware vsphere, KVM, and Xen. Management Templates, Aspects, and policies related to these technologies are not available from OMi MP for Infrastructure 2.00 version. For x86 Virtualization technologies, you can continue to use the virtualization component of the OMi MP for Infrastructure (versions earlier to 2.00) till the obsolescence of Operations Agent 11.1x. However, for non-x86 Virtualization technologies (VM, AIX, Solaris), you can continue to use the OMi MP for Infrastructure. Some of the key benefits that you get with the technology evolution to Cloud Optimizer are: Improved scalability and interoperability. Improved coverage of metrics. While the technology evolution entitles you to an equivalent capability replacement in Cloud Optimizer, you can get enhanced performance troubleshooting and capacity optimization of physical, virtual, and cloud technologies with the premium edition of Cloud Optimizer. For more details, see Marketplace.

15 Get started CustomerInformationPortal This section provides information about key concepts of OMi MP for Infrastructure. Key concept

16 Key concept CustomerInformationPortal The OMi Management Pack for Infrastructure (OMi MP for Infrastructure) works with Operations Manager i (OMi) and enables you to monitor the various systems operating in a data center environment. It includes Indicators - Health Indicators (HIs), Event Type Indicators (ETIs), and Topology Based Event Correlation (TBEC) Rules that analyze and categorize the events occurring in the systems and report the health status of the systems. It also includes Management Templates for monitoring the availability, health, and performance of individual systems, clusters, and virtual nodes. These Management Templates consists of a wide range of Aspects which enables to monitor the system components. The Management Templates can be deployed by administrators for monitoring the systems in any environment. The Management Templates can also be customized by subject matter experts (SMEs) and developers to suit different monitoring requirements. OMi MP for Infrastructure works with OMi and provides the following salient features: Ready-to-deploy, management solutions to suit different monitoring requirements. Aspects for creating customized solutions. Infrastructure element based deployment and configuration. Licensing No separate license is required for OMi MP for Infrastructure. Related Topics Infrastructure Management Templates Infrastructure Aspects Parameters

17 Install CustomerInformationPortal This section provides information about installing OMi MP for Infrastructure on OMi (Linux and Windows) servers. You can upgrade from any of the previous version to OMi MP for Infrastructure 2.00 version. Prerequisites OMi MP for Infrastructure Package Install OMi MP for Infrastructure version 2.00 Import OMi MP for Infrastructure AddOn Verify OMi MP for Infrastructure 2.00 Installation Configure OMi MP For Infrastructure Related Topic Upgrade

18 Prerequisites CustomerInformationPortal The following section lists the hardware and software prerequisites for installing OMi MP for Infrastructure on OMi (Linux or Windows) servers. Software Requirements The following components must be installed and configured on the OMi 10.x servers before you install the OMi MP for Infrastructure 2.00: Server Component Version Operations Manager i or later*

19 Managed Node Component Version Operations Agent or later*

20 SiteScope Server Component Version SiteScope or later*

21 User Privileges The user must have the local Infrastructure Administrator privileges assigned for the Infrastructure Admin Server. If you are using LDAP directory, you must create a user account similar to the user account of LDAP in the local Infrastructure instance and grant Administrator privileges to the user. Related Topic Support Matrix

22 OMi MP for Infrastructure Package CustomerInformationPortal The following section provides information about the installation package for OMi MP for Infrastructure The OMi MP for Infrastructure 2.00 is available at the web site Marketplace. The package is available for English and Non- English locale environments. You can use the appropriate installation media based on your locale requirements. The OMi MP for Infrastructure 2.00 contains the OMi MP for Infrastructure features, software and the product documentation. In a distributed environment, it must be installed on all OMi Data Processing Servers (DPS) and OMi Gateway Servers (GWS).

23 Install OMi MP for Infrastructure version 2.00 CustomerInformationPortal This section provides information about installing OMi MP for Infrastructure 2.00 on the OMi (Linux or Windows) servers. Downloading the OMi MP for Infrastructure 2.00 To download the OMi MP for Infrastructure 2.00, follow these steps: 1. Download the OMi_MP_for_Infrastructure_ zip package from:marketplace 2. Extract the installation package to a temporary location - Temp. Installing OMi MP for Infrastructure 2.00 using Command Line For Linux: 1. Log on as a root user. 2. Set the umask by typing the command umask Change the directory to extract the file to the Temp folder: 4. To install the package, run the following command:<path>/mpinstall.sh -ifor example, to install OMi MP for Infrastructure in Korean locale with OMi in Japanese locale, specify the following command:<path>/mpinstall.sh -i -locale konote You can use the following command options:<path>/mpinstall.sh -i [-locale <MP Locale>] [-h help]-i : Install Management Pack.-locale: Locale specific Management Pack to install.-h -help: Shows the help message.you can specify the <mplocale> as follows: de: German locale zh_cn: Simplified Chinese locale fr: French locale es: Spanish locale ko: Korean locale ru: Russian locale ja: Japanese locale 1. To accept the End User License Agreement (EULA), type Yes or Y and to decline the license agreement type No or N. fter the installation is completed, the following message appears: OMi Management Pack Installation Finished. For Windows: 1. Change the directory to extract the file to the Temp folder: 1. Open the command prompt, change the directory to the Temp directory, and run the following command:cscript /nologo mpinstall.vbs -ifor example, to install OMi MP for Infrastructure in Korean locale with OMi in Japanese locale, specify the following command:cscript /nologo mpinstall.vbs -i -locale ko 2. To accept the End User License Agreement (EULA), type Yes or Y and to decline the license agreement type No or N.Note If you decline the EULA, the OMi Management Pack will not be installed. After the installation is completed, the following message appears: OMi Management Pack Installation Finished.

24 Import OMi MP for Infrastructure AddOn CustomerInformationPortal The OMi MP for Infrastructure AddOn enables the collect and forward system log data only for Linux. The log streaming is available only for OMi version or later and is supported only from Operations Agent or later. By default, the data collection frequency is set to 1 minutes. Additionally, the OMi MP for Infrastructure AddOn contains policies and Aspect that enables you to collect and forward log data to reqruied targets. To configure policies for log streaming, see the section Configure Streaming of Logs. Follow these steps to install the content pack for Infrastructure AddOn: 1. In the OMi console, click Administration > Setup and Maintenance > Content Packs. 2. In the Content Pack Definitions pane, click Import Content Pack Definitions and Content. 3. In the Import Content Pack dialog box, click Browse and select the OMi_MP_for_Infrastructure_LogStreaming_AddOn_ file and then click Open. 4. Click Import to start the import.

25 Verify OMi MP for Infrastructure 2.00 Installation CustomerInformationPortal This section provides information about verifying the installation of OMi MP for Infrastructure on OMi 10.x (Linux and Windows) servers. You can perform any of the following checks to verify the OMi MP for Infrastructure 2.00 installation: Check the log files for any errors on OMi 10.x GWS, OMi 10.x DPS, and OMi 10.x typical servers at the following locations:for Linux: /opt/hp/bsm/log/mpinstall.logfor Windows: %TOPAZ_HOME%\log\mpinstall.logNote The OMi logs are available on both GWS and DPS at the following location:on OMi 10.x:For Linux: /opt/hp/bsm/log/jboss/opr-webapp.logfor Windows: %TOPAZ_HOME%\log\jboss\opr-webapp.log Check the following location on the OMi 10.x console:click Administration > Setup and Maintenance > Content Packs.The OMi MP for Infrastructure for 2.00 must appear in the Content Packs Definitions pane.

26 Configure OMi MP For Infrastructure CustomerInformationPortal The following section provides step-by-step instructions on how to get started using OMi MP for Infrastructure: Task 1: Adding Nodes to the OMi Console Note If the Node already exists in Run-time Service Model (RTSM), you can skip this step and proceed to Task 2. Before you begin monitoring, you need to add the nodes to the OMi console. 1. Open the Management Templates & Aspects pane:administration > Setup and Maintenance > Monitored Nodes 2. In the Node Views pane, click Predefined Node Filters > Monitored Nodes and click and then click Computer > Windows or Unix. The Create New Monitored Nodes dialog box appears. 3. Specify the Primary DNS Name, IP address, Operating System, and Processor Architecture of the node and click OK.The newly created node is saved as a CI instance in RTSM.The Node with Operations Agent needs to be activated to OMi server and certificate needs to be granted. Task 2: Deploying the Infrastructure Discovery Aspect To discover the CIs on the added managed nodes, you must deploy the Discovery aspect. 1. Open the Management Templates & Aspects pane:administration > Monitoring > Management Templates & Aspects 2. In the Configuration Folders pane, click Configuration Folders > Infrastructure Management Templates. 3. In the Management Templates & Aspects pane, right-click the respective Infrastructure discovery aspect, and then click Assign and Deploy Item. The Assign and Deploy Wizard opens. 4. In the Configuration Item tab, click the CI to which you want to deploy the Discovery aspect and then click Next. 5. In the Required Parameters tab, all mandatory parameters are listed in the management template that do not have a value.if all required values are specified, click Next to go to Parameter Summary.To change a parameter, double-click it, or click a. Select the Instance parameter in the list, and then click. The Edit Parameter Value dialog box opens. b. Click Value, specify the value, and then click OK. c. Select the Dependent Parameters and specify the value. Click Next. 6. In the Parameter Summary tab, you can change the default values of the parameters. To edit the parameters, follow these steps: a. Double-click the parameter, or select the parameter from the list, and then click. b. The Edit Parameter window opens. Change the default value and click OK. Click Next. 7. Click Value, specify the value, and then click OK. Click Next. 8. Optional. If you do not want to enable the assignment immediately, clear the Enable Assignment(s) check box. You can then enable the assignment later using the Assignments & Tuning pane. 9. Click Finish.A status message is displayed. To check the status of the deployment jobs, go to Administration > Monitoring > Deployment Jobs. Task 3: Verifying the Discovery After you deploy the Infrastructure Discovery Aspect, you must verify if the CIs are populated in the Top view. To view the CIs populated in the View, follow these steps: 1. In the OMi Console, click Workspaces > Dashboards > View. 2. From the drop-down list, select View. The View page appears. 3. In the View page, select HACluster_Infrastructure, Sol_Zones_Infrastructure, or Systems_Infrastructure view. The CIs are populated in the View.

27 Task 4: Deploying the Infrastructure Management Templates or Infrastructure Discovery Aspects Note If you are using Monitoring Automation for Composite Applications license, you can either deploy the Infrastructure Management Templates or Infrastructure Aspects to the CIs. If you are using Monitoring Automation for Servers license, you can deploy the Infrastructure Aspects. Task 4a: Identifying and Deploying Infrastructure Management Template You must deploy the Infrastructure Discovery Aspect even if the CIs are already populated by any other source such as SiteScope, DDM, and so on. To deploy the Infrastructure Management Templates to the CIs, follow these steps: 1. Open the Management Templates & Aspects pane:administration > Monitoring > Management Templates & Aspects 2. In the Configuration Folders pane, click Configuration Folders > Infrastructure Management > Infrastructure Management Templates. 3. In the Management Templates & Aspects pane, click the Management Template that you want to deploy, and then click Assign and Deploy item. The Assign and Deploy wizard opens. 4. In the Configuration Item tab, click the CI to which you want to assign the Management Template, and then click Next. 5. In the Required Parameters tab, all mandatory parameters are listed in the management template that do not have a value.if all required values are specified, click Next to go to Parameter Summary.To change a parameter, double-click it, or click. a. Select the Instance parameter in the list, and then click. The Edit Parameter Value dialog box opens. b. Click Value, specify the value, and then click OK. c. Select the Dependent Parameters and specify the value. Click Next. 6. Click Next to go to Parameter Summary. To change the default values of the parameters, you can select the parameter and then click. The Edit Parameter dialog box opens. Click Value, specify the value, and then click OK. Click Next.Note In the Parameter Summary tab, you can override the default values of any parameter. You can specify a value for each parameter at the Management Template level. By default, parameters defines as expert parameters are not shown. To show expert parameters, click Hide / Unhide Expert Parameters. 7. Click Value, specify the value, and then click OK. Click Next. 8. Optional. In the Configure Options tab, if you do not want to enable the assignment immediately, clear the Enable Assignment(s) check box. You can then enable the assignment later using the Assignments & Tuning pane. 9. Click Finish. Note Monitoring configurations are not automatically updated with the versions of Policy Templates, Management Templates, and Aspects uploaded with the Management Pack. To update the versions, you can use the Update to Latest feature. Task 4b: Deploying Infrastructure Aspects You must deploy the Infrastructure Discovery Aspect even if the CIs are already populated by any other source such as SiteScope, DDM, and so on. Note If you are using Monitoring Automation for Composite Applications license and have assigned the Infrastructure Management Templates to the CI, you can skip this task. 1. Open the Management Templates & Aspects pane:administration > Monitoring > Management Templates & Aspects 2. In the Configuration Folders pane, select Configuration Folders > Infrastructure Management > Infrastructure Management Templates. 3. In the Management Templates & Aspects pane, select the Aspect you want to deploy, and then click Assign and Deploy Item. The Assign and Deploy wizard opens. 4. In the Configuration Item tab, select the CI to which you want to assign the Aspect and then click Next. 5. In the Required Parameters tab, all mandatory parameters are listed in the management template that do not have a value.if all required values are specified, click Next to go to Parameter Summary.To change a parameter, double-click

28 it, or click. a. Select the Instance parameter in the list, and then click. The Edit Parameter Value dialog box opens. b. Click Value, specify the value, and then click OK. c. Select the Dependent Parameter and specify the value. Click Next. 6. In the Parameter Summary tab, you can change the default values of the parameters. To edit the parameters, follow these steps: a. Double-click the parameter, or select the parameter from the list, and then click. b. The Edit Parameter window opens. Change the default value and click OK. 7. Optional. In the Configure Options tab, if you do not want to enable the assignment immediately, clear the Enable Assignment(s) check box. You can then enable the assignment later using the Assignments & Tuning pane. 8. Click Finish. Monitoring Infrastructure Environment After you deploy Management Template and Aspects, you can analyze the status and health of Infrastructure CIs from the following perspectives: Event Perspective Health Perspective Performance Perspective Event Perspective The Event Perspective provides complete information of events. In the Event Perspective, you can view the event information of the Oracle CI that are monitored by OMi Management Pack for Infrastructure. To view the Event Perspective of Infrastructure CIs, follow these steps: 1. Open the Event Perspective pane and click Workspaces > Operations Console > Event Perspective. 2. In the Browse Views tab, select the Systems_Infrastructure view that contains the Infrastructure CIs for which you want to view the events. Alternatively, you can use e Search tab to find an Infrastructure CI. 3. Click the Infrastructure CI for which you want to view the Event Perspective. The list of events for the selected Infrastructure CI appears on the Event Browser pane.when you click an event from the Event Browser pane, the Event Details pane opens where you can view the following details: General - Displays the detailed information about the selected event such as Severity, Lifecycle State, Priority, Related CI and so on. Additional Info - Displays more detailed information about the attributes of the selected event. Source Info - Displays an overview of the information available about the source of the selected event. Actions - Displays the list of actions available for a selected event. There are two types of possible actions: User Action and Automatic Action. Annotations - Displays a list of the annotations attached to the selected event. Custom Attributes - Displays a list of the attributes that either an administrator or the responsible user manually configured and added to the selected event. Related Events - Displays an overview of all the events that are related to the event selected in the Event Browser. History - Displays the history of the selected event. Resolver Hints - Displays the information used to identify the node and CI associated with an event. Instructions - Displays instructions designed to help operators handle the associated event. Forwarding - Displays the transfer of ownership details if any, for the events. Health Perspective The Health Perspective provides a high-level view of the overall health information of the related CIs in the context of events. In the Health Perspective, you can view the health information of the Infrastructure CIs that are monitored by OMi MP for Infrastructure. To view the Health Perspective of Infrastructure CIs, follow these steps: 1. Open the Health Perspective pane and click Workspaces > Operations Console > Health Perspective. 2. In the Browse Views tab, select the Systems_Infrastructure view that contains the Infrastructure CIs for which you

29 want to view the health-related events. Alternatively, you can use the Search tab to find an Infrastructure CI. 3. Click the Infrastructure CI for which you want to view the Health Perspective. The list of health-related events for the selected Infrastructure CI appears on the Event Browser pane.when you click an event from the Event Browser pane, the following panes appear: Health Top View - Displays the health top view of the selected event. Health Indicators - Displays the Key Performance Indicators (KPIs) and HIs related to the CI that you select from the Health Top View pane. Actions - Displays the list of actions available for a selected event. Performance Perspective The Performance Perspective enables you to populate graphs from existing graph templates. You can also plot customized graphs by selecting the required metrics for a specific CI. To view the Performance Perspective of Infrastructure CIs using graphs, follow these steps: 1. Open the Performance Perspective pane and click Workspaces > Operations Console > Performance Perspective. 2. In the Browse Views tab, select the Systems_Infrastructure view. The list of CIs appear. Select a specific CI. The Performance pane appears, which lists the default graphs available for the Systems_Infrastructure view. 3. Click the graph you want to plot from the Graphs tab, and then click Draw Graphs. The selected graph is plotted on the right pane. Related Topic Customizing Infrastructure Management Template

30 Upgrade CustomerInformationPortal This section provides information about upgrading OMi MP for Infrastructure from previous version to 2.00 version. You can upgrade to 2.00 from any of the previous version. Update the Management Templates and Aspects to a Newer Version You can update the already deployed Management Templates and Aspects to the latest version. OMi MP for Infrastructure 2.0 contains the following new aspects. You must perform configuration before deploying these aspects. Adaptive Thresholding Change Configuration Monitor Key System Service Availability Operations Agent Self Monitoring Realtime Resource Bottleneck Performance Collection Component The following are two scenarios when you need to update the Management Templates or Aspects: Use Case 1: You have already deployed Infrastructure Aspects and/or Management Templates to the managed nodes before installing OMi MP for Infrastructure We recommend you to use the latest version of Aspects or Management Templates on those nodes. To update to the latest version, select the Management Templates or Aspects on the managed nodes. Perform the following steps for each Management Template and Aspect assignment on each of the managed nodes: 1. Open the Assignments & Tuning pane and click Administration > Monitoring > Assignments & Tuning. 2. In the Browse Views pane, select the Infrastructure_Common view and select each Node CI where version update is required. 3. Click Show Assignments That Require an Update.All the Management Templates and Aspects that requires an update are listed. 4. Select each of the Management Templates and Aspects and click Update Assigned Item.The Update Assigned Item dialog box appears. 5. In the Update Options tab, follow these steps: Select the latest version from the Update to Version drop down list. If you select Use parameter values from existing assignments, only the new mandatory parameters that do not have a default value are listed. If you select Use default parameter values from version selected above, all mandatory parameters from the selected Management Template or Aspect version that do not have a default value are displayed. These parameters must be edited before proceeding to the next step of the wizard. 6. Click Next to go to Required Parameters.To change a parameter, double-click or select the parameter from the list and click Edit.The Edit Parameter dialog opens. If there are no mandatory parameters that require editing for this assignment, you are automatically taken to the Parameter Summary tab. 7. Click Next to go to Parameter Summary tab, or click Finish to save the changes and close the wizard. 8. Click Finish to save the changes and close the wizard. The assigned item is updated to the specified Management Template or Aspect version. Use Case 2: You are using a Management Pack that internally uses the OMi MP for Infrastructure Aspects and you need to update the Infrastructure Aspects to the latest version. For example, OMi MP for Oracle Database, OMi MP for Oracle WebLogic, OMi MP for Microsoft Exchange Server, OMi MP for SAP, and so on use Infrastructure Aspects to monitor Infrastructure performance such as Resource Bottleneck Diagnosis, System Fault Analysis and so on. To update all items in a Management Template of OMi Servers, do the following:

31 1. Open the Management Templates & Aspects pane:click Administration > Monitoring > Management Templates & Aspects. 2. Select each Management Template that contains the Infrastructure Aspects. 3. Click Update to Latest.The Update to Latest Wizard appears. 4. In the Options tab, click Next. 5. In the Preview tab, a preview of the update is shown as an expanded tree view of the Aspect, where items that will be updated are labeled "(old version > new version)", and items that will not be updated are labeled "(current version)". 6. Click Finish to apply the update as shown in the preview. To update the latest version of Management Templates on the managed nodes: 1. Click Administration > Monitoring > Assignments & Tuning. 2. In the Browse Views pane, select the specific application view and select each CI where version update is required. 3. Click Show Assignments That Require an Update.All the Management Templates and Aspects that requires an update are listed. 4. Select each Management Templates and click Update Assigned Item.The Update Assigned Item dialog box appears. 5. In the Update Options tab, follow these steps: Select the latest version from the Update to Version drop down list. If you select Use parameter values from existing assignments, only the new mandatory parameters that do not have a default value are listed. If you select Use default parameter values from version selected above, all mandatory parameters from the selected management template or aspect version that do not have a default value are displayed. These parameters must be edited before proceeding to the next step of the wizard. 6. Click Next.To change a parameter, double-click or select the parameter from the list and click Edit.The Edit Parameter dialog opens. If there are no mandatory parameters that require editing for this assignment, you are automatically taken to the Parameter Summary tab. 7. Click Next or Finish to save the changes and close the wizard. 8. Click Finish to save the changes and close the wizard. The assigned item is updated to the specified management template or aspect version. Related Topic Administer Install

32 Administer CustomerInformationPortal This section provides information about configuration required before deploying the management templates and aspects. After discovering the environment, if you want to monitor Adaptive Thresholding, Change Configuration, Real-time resource bottleneck or stream logs for analytics, then complete the following configuration before deploying the management template or aspect. Customizing Infrastructure Management Templates Configure Adaptive Thresholding Aspect Configure Change Configuration Monitor Aspect Configure Key System Service Availability Aspect Configure Realtime Resource Bottleneck Aspect Configure Streaming of Logs

33 Customizing Infrastructure Management Templates CustomerInformationPortal OMi MP for Infrastructure can be customized to suit your monitoring requirements. You can edit the existing Infrastructure Management Templates or create new Infrastructure Management Templates to monitor the systems in your environment. The following section provides information about the customization scenarios for OMi MP for Infrastructure. Creating Infrastructure Management Templates Editing Infrastructure Management Templates

34 Creating Infrastructure Management Templates CustomerInformationPortal 1. Open the Management Templates & Aspects pane:click Administration > Monitoring > Management Templates & Aspects. 2. In the Configuration Folders pane:configuration Folders > Infrastructure Management > Infrastructure Management Templates 3. If you need to create a new configuration folder, click. The Create Configuration Folder opens. 4. Type the name of the new configuration folder and the description. For example, you can type the new configuration folder name as Test. 5. Click OK. The new configuration folder is created.configuration Folders > Infrastructure Management > Test 6. Select the new configuration folder. In the Management Templates & Aspects pane, click. The Create Management Template wizard opens. 7. In the General tab, type a Name for the new Management Template. Click Next. 8. Select a Topology View that shows the CI type that you want to manage, and all the related CI types. Click an item in the topology map to select the CI Type of the CIs that this Management Template enables you to manage. You can assign the type of CI to a Management Template. For example, you can select Systems_Infrastructure as the topology view and Computer as the CI Type. Click Next. 9. In the Aspects tab, click, and then click to add existing Aspects to the new Management Template. The Add Existing Aspect dialog box opens. Select the Aspects that you want to add, and then click OK.If suitable Aspects do not exist, click, and then click to create an Aspect. 10. For each Aspect that you add, you must specify at least one Target CI.Click an Aspect in the list, and then in the topology map, click the CI types you want the Aspect to monitor when this Management Template is assigned. (Press CTRL to select several CI types.) Each CI type that you select here must correspond to one of the CI types assigned within the Aspect itself (or a child of one of those CI types). For example, you can select CI from the topology map. 11. In the Parameters tab, the list of all the parameters added to this Aspect from the policy templates is displayed.to combine the parameters: 1. Press CTRL and click the parameters that you want to combine. 2. Click. The Edit/Combine Parameters dialog box opens. 3. Type a Name for the combined parameters. 4. (Optional). Specify a Description, Default Value, and whether the combined parameter is Read Only, an Expert Setting, or Hidden.You can specify either a specific default value, or you can click From CI Attribute and then browse for a CI attribute. When you specify a CI attribute, Operations Management sets the parameter value automatically during the deployment of the underlying policy templates, using the actual value of this attribute from the CI. You can also change values of conditional parameters. (The conditions are read-only and cannot be changed at Management Template level.)note Read Only prevents changes to the parameter value when the Aspect is assigned to a configuration item. Hidden also prevents changes, but additionally makes the parameter invisible. Users can choose whether to show expert settings when they make an assignment. 5. Click OK. You can also edit the parameters without combining them, to override the defaults in the Aspects or policy templates. Click one parameter, and then click. The Edit/Combine Parameters dialog box opens. 12. In the Create Management Template wizard, click Finish to save the Management Template and close the wizard. The new Management Template appears in the Management Templates & Aspects pane.

35 Editing Infrastructure Management Templates CustomerInformationPortal You can edit the Management Templates to change the following artifacts: Editing Parameters - Changing the default values Editing Aspects - Deleting an Aspect Editing Parameters - Changing the Default Values Use Case: You are using Essential System Management Template to monitor the health of every single system in the datacenter. You are monitoring the availability and utilization of the system resources in your environment. You want to modify the parameters corresponding to the resources of the system like hardware and software to closely monitor the health of the system. To edit the parameters: 1. Open the Management Templates & Aspects pane:click Administration > Monitoring > Management Templates & Aspects. 2. In the Configuration Folders pane:configuration Folders > Infrastructure Management > Infrastructure Management Templates > Essential System Management 3. In the Management Templates & Aspects pane, select Essential System Management from the list, and then click. The Edit Management Template dialog box opens. 4. Click the Parameters tab. The list of parameters appear. a. Double-click the desired parameter. The Edit/Combine Parameters window appears. b. You can change the default value by clicking. c. Specify the value and click OK. The Edit Management Template dialog box opens. d. Click OK. The version of the Management Template is incremented. Note The version number of the Management Template is incremented when any customization is made to the Management Template. Editing Aspects - Deleting an Aspect Use Case: You are using Extensive System Management Template to monitor the performance of systems in a datacenter. You are monitoring the performance of all system resources like CPU, memory, disk, filesystem, network interface, system process and services, security, system logging and so on. You do not want to use some Aspects which are part of the Extensive System Management Template. To edit the Aspects: 1. Open the Management Templates & Aspects pane:click Administration > Monitoring > Management Templates & Aspects. 2. In the Configuration Folders pane:configuration Folders > Infrastructure Management > Infrastructure Management Templates 3. In the Management Templates & Aspects pane, select Extensive System Management from the list, and then click. The Edit Management Template dialog box opens. 4. Click the Aspects tab. The list of Aspects appear. 5. Select the Aspect that you want to delete from the list. 6. Click to delete the selected Aspect. 7. Click OK. The version of the Management Template is incremented.

36

37 Configure Adaptive Thresholding Aspect CustomerInformationPortal This section includes overview and configuration for adaptive thresholding. Adaptive Thresholding Aspect is compatible with Operations Agent or later. Baseline data computed by Operations Agent is used by the Sys_AdaptiveThresholdingMonitor policy to monitor performance and resource utilization. The Aspect contains a ConfigFile and a Measurement Threshold policies. You must tune the policies to specify the required baseline metric and deviation. Prerequisite for Deploying Perform following tasks before deploying the Aspect: 1. Enable baselining in Operations Agent.By default, baselining is disabled on the Operations Agent node. You can enable baselining either through command line or configuration file.to enable base using the configuration file, follow the steps: 1. Open the Policy Template pane:administration > Monitoring > Policy Template. 2. In the Policy Template Groups pane, expand Policy Management > Templates grouped by type > Configuration > Node Info. 3. In the Policy Templates pane, select the OPC_PERL_INCLUDE_INSTR_DIR policy and click. The Edit Node Info Policy window opens. 4. In the Policy Data pane, at the end add the following lines:[oacore] ENABLE_BASELINE=TRUE 5. Click Save and Close. Baseline data is computed only at the end of every hour. If you want the baseline data to be computed immediately after you enable baseline, you must restart the oacore process. Run the following command to restart oacore: ovc -restart oacore 2. Define metrics to create baseline metrics. Based on the classes defined in the baseline.cfg file, corresponding baseline classes are created in the Metrics Datastore. For every metric specified in the baseline.cfg file, sixteen baseline metrics are created. The original baseline.cfg file is available at %OvDataDir%/conf/sispi/configuration location. The baseline.cfg file is overwritten after the ConfigFile policy is deployed. 3. Decide where the deviation is required. You can configure deviations (N) either in the Sys_ConfigureBaselining policy or in the Sys_AdaptiveThresholdingMonitor policy. To configure deviations for specific metrics, set the deviations in the Sys_ConfigureBaselining policy. To configure deviations for all metrics, set the deviations in the Script-Parameters tab in the Sys_AdaptiveThresholdingMonitor policy. If no deviations are set for a metrics in the Sys_ConfigureBaselining policy, then the deviations set in the Sys_AdaptiveThresholdingMonitor policy are used to calculate adaptive threshold values. 4. Edit Sys_ConfigureBaselining ConfigFile policy to specify single deviation. 1. Open the Management Templates & Aspects pane: Click Administration > Monitoring > Management Templates & Aspects. 2. In the Configuration pane, expand Configuration Folders > Infrastructure Management > System Infrastructure Aspects. 3. In the Management Templates & Aspects pane, select the Adaptive Thresholding Aspect and click. The Edit Aspect window opens. 4. In the Policy Templates tab, double-click Sys_ConfigureBaselining policy. The Edit ConfigFile Policy window opens. 5. In the Policy Data tab, specify class, metric and deviation in the following format. <Class>:<Metric>,<Warning Deviation>,<Minor Deviation>,<Major Deviation>,<Minimum Value>,<Maximum Value>,<CutOff> In this instance: <Class> is the metrics class. <Metric> is the metrics for which baseline data must be computed. Only class and metric are mandatory. You can define deviation for specific instance for instance based monitoring. For Example, dsk0,0.1,0.2,0.3,0,100,20 dsk1,0.2,0.3,0.4,0,100,15 dsk2:exclude For every group, one corresponding CFG file is created. The CFG files are automatically deleted once the instance metric are delete in the policy.

38 6. Click Save and Close. 5. Edit Sys_AdaptiveThresholdingMonitor policy for defining deviation for each metric. 1. Open the Management Templates & Aspects pane: Click Administration > Monitoring > Management Templates & Aspects. 2. In the Configuration pane, expand Configuration Folders > Infrastructure Management > System Infrastructure Aspects. 3. In the Management Templates & Aspects pane, select the Adaptive Thresholding Aspect and click. The Edit Aspect window opens. 4. In the Policy Templates tab, double-click Sys_AdaptiveThresholdingMonitor policy. The Edit ConfigFile Policy window opens. 5. In the Policy Data tab, you can modify the default parameters in the Policy Parameters tab. 6. Click Save and Close. 6. Include the latest version of policies in Aspect and deploy.

39 Configure Change Configuration Monitor Aspect CustomerInformationPortal This section includes overview and configuration for monitoring change in system configuration. Change Configuration Monitor Aspect monitor files, Windows registry settings, and command outputs for changes. On deploying the Change Configuration Monitor Aspect, a ccilist.cfg file is created in the <OvDataDir>/ccimon/configuration folder. The Sys_ChangeConfigurationMonitor policy reads the ccilist.cfg file to monitor the following changes on the system: Software installed, removed or modified Patches/service packs/updates installed Changes to Kernel parameters Boot configuration Registry key for Windows only Kernel image file All user accounts System service configuration, Shared directories, NFS or CIFS (samba) mounts added, modified or removed System environment variables CCI and Desired State Monitoring In both CCI and desired State monitoring method; files, Windows registry settings, and command outputs are monitored for changes. Comparison method in both the process is as following: CCI Monitoring During the first polling interval, backup of all the files specified in the ccilist.cfg file. From the consecutive polling, a comparison is performed between current version and backup version of files. Alerts are generated if modification is identified. The backup files are overwritten with fresh backup. Comparison is always between current version and recent backup version of files. Desired State Monitoring A gold file (with extension.gold) must be created for every single file that must be monitored and must be available in the same directory as the file. A gold file is a backup or reference file that remains unchanged. For example, let us consider that you want to monitor the mtab file located in the /etc directory. Take a backup of this file and save it as mtab.gold in the /etc directory. This is your reference file or gold file which does not change. To monitor the mtab file add the following to the configuration file: /etc/mtab==/etc/mtab.gold,file,os,,major. After deploying the Aspect, a check is performed to verify if desired state monitoring is defined in the ccilist.cfg configuration file. A comparison is performed for the files, windows registry settings, and command outputs specified in the configuration file with the corresponding gold file. Alerts are generated whenever there is a difference is identified between the two files.

40 Note Make sure that you define Desired State Monitoring in ConfigFile only after creating the gold file. You must tune one of the following policies based on the Operating System of the node to specify CCI or desired state monitoring: Sys_MSWindowsChangeConfig Sys_SunSolarisChangeConfig Sys_LinuxChangeConfig Sys_HPUXChangeConfig Sys_AIXChangeConfig Tuning ConfigFile Policy Edit and configure ConfigFile policy for defining the change monitoring. 1. Open the Management Templates & Aspects pane:click Administration > Monitoring > Management Templates & Aspects. 2. In the Configuration pane, expand Configuration Folders > Infrastructure Management > System Infrastructure Aspects. 3. In the Management Templates & Aspects pane, select the Change Configuration Monitor Aspect and click. The Edit Aspect window opens. 4. In the Policy Templates tab, double-click the required policy. The Edit ConfigFile Policy window opens. 5. In the Policy Data tab, specify class, metric and deviation in the following format.change ci key,cci type (file cmd),msg group,backup filename,alert severity In this instance: <change ci key> - Specifies a registry key, a command or a file name with complete path. <cci type> - Set this to the following values - cmd, regkey, or file based on the change ci key. Registry key (regkey) type is available only for Windows managed nodes. <msg group> - Specifies the OMi message group setting for the change alert. The default message group is Misc. <backup filename> - This is the name with which a backup file is created in the backup folder. The backup file created is used for comparisons with the parent file (provide empty value for monitoring CCI type 'file'). (not required for cci type file) Backup folder is located in the<ovdatadir>/tmp file. <alert severity> - Specifies the OMi alert severity setting. The default alert severity is Warning. 6. Click Save and Close. Examples for CCI and Desired State Monitoring CCI Monitoring Scenario To monitor the hosts file on Windows and send warning alerts with misc message group To monitor the sys-temp folder on Windows for any changes To monitor a registry key and its values on Windows On Windows, to monitor if opcmona.exe process is running on a node and if it is different from the last run To monitor if there are any new files or other changes in /tmp folder on Linux To monitor if there are any user changes on UNIX/Linux Syntax in ConfigFile c:\windows\system32\drivers\etc\hosts,file,misc,,warning dir "%temp%" findstr /V bytes,cmd,os,dirtmpbin,warning HKEY_LOCAL_MACHINE\SOFTWARE\CCIMon,regkey,misc,temp,warning wmic process where name='opcmona.exe' get processid,cmd,os,notepadproc, major,unicode sort -u,cmd,misc,ls1tmp.txt,warning /etc/passwd,file,security,,warning

41 To check for new filesystems mounted on UNIX/Linux /etc/mtab,file,os,,minor

42 Desired State Monitoring Scenario Syntax in ConfigFile To monitor the hosts file on Windows and Syntax: filename==reference file name,ccitype,msg group,[backup send warning alerts to a filename],alert severity,charset miscellaneous message Example: /etc/mtab==/etc/mtab.gold,file,misc,,warning group To monitor a folder on Windows for any changes, use the command type cmd for change tracking To monitor a registry key and its values on Windows Syntax: command==path of the file containing command output,ccitype,msg group,[backup filename],severity Example: ls /==/root/list.txt,cmd,misc,,major Syntax: Registry key=='value of registry key',ccitype,msg group,[backup filename],severity Example: HKEY_LOCAL_MACHINE\SOFTWARE\config==config,regkey,misc,,warning

43

44 Configure Key System Service Availability Aspect CustomerInformationPortal This section includes overview and configuration for monitoring availability of key system services. The Aspect monitors the key processes that run in the background to support the different tasks required for the operating system or application. The Sys_ProcessMonitor policy monitors all the process in the process groups. In the Sys_ProcessMonitorConfig policy, you must specify the process group and location of the procmon.cfg configuration file. You can specify the process group and location of the procmon.cfg configuration file while deploying the Aspect as optional parameters. Alerts are generated whenever the processes defined in the configuration file either do not run as expected or the processes are out of limits during the specified time of the day and day of the week. After the Aspect is deployed, if the procmon.cfg file is available in the location specified in Sys_ProcessMonitorConfig policy, then the file is overwritten. If the file is not available, then a new file is created in the designated location. Prerequisites Following is a syntax for editing Sys_ProcessMonitorand Sys_ProcessMonitorConfig policies before deploying. Syntax for ConfigFile Policy [ProcessGroupName] Process name<tab>argument<tab>time of the day<tab>days of Week<tab>Bounds In this instance, Process Name: Specifies the name of the process to be monitored. Arguments: Specifies the arguments that are used to distinguish between multiple processes running simultaneously. If no arguments are present, an asterisk (*) must be specified. Time of the day: Specifies the time duration (in the 24-hour format) during which a process failure must be reported. Day of Week: Specifies the day or days to report process failure. Each day of week is identified with a number as listed in the table. 0 being Sunday and 6 being Saturday. Numbers should be separated by commas. Bounds: Specifies the number of instances of named processes. You can specify the number of instance as follows:n: An exact numbern: A minimum of n-n: A maximum of nm-n: A range of m to severity: Specifies the severity of alert messages such as Minor, Major or Critical. Default severity is Specifies the command (<cmd>) that must be run during a process failure. Scenarios and syntax for customizing ConfigFile policy: Scenario To monitor processes all week during every polling interval To monitor processes with more than one argument Sample Syntax [ProcessGroupName] processname<tab>argument<tab>processlimits /opt/ov/lbin/eaagt/opcmona * 1 Syntax: pr3ocessname<tab>argument1<space>argument2<tab>processlimits Arguments should be separated with space. Example: [OMi_Mgt] /opt/ov/bin/oacore oacore /var/opt/ov/conf/oa/pipedefinitions/oacore.xml 1

45 To monitor processes only at specified time of the day or day of the week To mention the severity of the alert message To mention operator initiated command Syntax: [ProcessGroupName] processname<tab>argument<tab>timeoftheday<tab>daysofweek<tab>processlimits Example: [OMi_Mgt] /opt/ov/lbin/agtrep/agtrep -start ,1,2,3 1 Syntax:@severity=<severity> severity can be warning,minor,major,critical to be executed> -start agtrep

46

47 Configure Realtime Resource Bottleneck Aspect CustomerInformationPortal This section includes overview and configuration for monitoring real-time resource bottleneck. Prerequisite for deploying the aspect: RealtimeAlerts policy detects 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 production environment. Also, mention the metrics used and that the policy reads the adv.out file which is a result of the output of advisor.pl file. Note You must enable RTMA license on the Operations Agent node for RealTimeAlerts policy to fetch real time data. Prerequisite for deploying the aspect: You must increase the agent timeout to avoid termination of process before completion of aspect deployment. Follow these steps to increase the timeout: 1. Stop the Operations Agent process, run the following command:ovc -kill 2. Edit the default timeout, run the following command:ovconfchg -ns eaagt -set OPC_CONFIGFILE_TIMEOUT Set the control notification to true, run the following command: ovconfchg -ns conf.core set ASYNC_CONTROL_NOTIFY TRUE 4. Start the Operations Agent process, run the following command: ovc start

48 Configure Streaming of Logs CustomerInformationPortal This section includes overview and configuration for streaming the system logs. OMi MP for Infrastructure enables data collection from system log file. The log data is structured in a specific format to provide information about timestamp, host, and message. The structured data is further processed by Operations Agent and forwarded to required targets (example, Operations Bridge Analytics). Operations Bridge Analytics can use these logs to predict trends and pinpoint issues in your IT environment. OMi MP for Infrastructure provides System Log Collection aspect that enables the streaming of structured logs for both Linux-based and Windows event logs. The System Log Collection Aspect and the related policies are available as OMi MP for Infrastructure AddOn package. Note Log streaming for Linux based system logs is supported from Operations Manager i (or later) and Operations Agent (or later) versions and Windows based system logs is supported from Operations Manager i (or later) and Operations Agent (or later) versions. System Log Collection Aspect contains Log Streaming and Data Forwarding policies that must be configured prior to deploying the aspect. Data from the log file is converted to structured data based on the mapping and conditions defined in the Log Streaming policy. Operations Agent processes the data and forwards it to the target specified in the Data forwarding policy. Hence, before deploying the data collection aspect, make sure that the policies are configured. Policy template System Supported mode Operations Manager i Operations Agent Sys_SyslogStreaming Linux Normal mode (or later) (or later) Sys_ApplicationlogStreaming Windows Raw mode (or later) (or later) Sys_SecuritylogStreaming Windows Raw mode (or later) (or later) Sys_SystemlogStreaming Windows Raw mode (or later) (or later) Sys_DataForwarding Linux and Windows Normal mode (or later) (or later) Sys_CustomlogStreaming Windows Raw mode (or later) (or later)

49 For more information on policy templates of System Log Collection Aspect, see Systems Infrastructure Aspects. Custom logs for windows On your windows system, you may have define custom logs. The Sys_CustomlogStreaming policy template helps you stream these custom logs to the required target for further analysis. The Sys_CustomlogStreaming takes Log Name, mentioned in your windows custom log, as parameter. You can define as many custom logs as required. However, ensure to duplicate the Sys_CustomlogStreaming policy template for each of the log types, and then provide the log file path as parameter. On your windows system, if you have defined custom logs for hardware events, application events and services, duplicate the Sys_CustomlogStreaming policy template for each of these custom logs, and then provide the Log Name in Custom_logpath of Sys_CustomlogStreaming policy template. For example, on your windows system, you may have defined custom logs for Microsoft PowerShell with Log Name as Microsoft-Windows-PowerShell/Operational. Mention the Microsoft-Windows-PowerShell/Operational in Custom_logpath of Sys_CustomlogStreaming policy template. To provide the log name path, follow these steps: 1. Go to Administration > Monitoring > Policy Template > Generic > Generic output from Windows Event Log. The list of all the policy templates are displayed in the Policy Template pane. 2. Duplicate the Sys_CustomlogStreaming policy template for the custom logs. 3. Select the custom log policy template and click. The Assign and Deploy wizard is displayed. 4. Click Next to display Required Parameter tab. 5. Click to edit the Value for Custom_logpath. The Edit Parameter window is displayed. 6. In the Value, enter the Log Name and save the changes. For example, if the Log Name in the Event Viewer is Microsoft-Windows-PowerShell/Operational.