Intelligent Management Center (IMC) is a converged network management product that manages resources, users, and services. It provides network management solutions based on the IMC platform and service components.

Application Manager (APM) is a resource component of IMC that monitors applications in a data center. During the monitor process, APM collects monitor index data and then generates application monitor reports. You can use the monitor reports to locate application performance bottlenecks and ensure available, reliable, and continuous services. The collected monitor data can also be used for further analysis of other IMC services.

Application scenario

As shown in Figure 1, applications are deployed on each server in the server clusters to provide services to users. APM is located on the network to monitor these applications.

Figure 1 Network diagram

Applications monitored by APM

This section describes applications that can be monitored by APM, common monitor, and specific monitor.

Monitored applications

Table 1 lists applications that can be monitored by APM.

Table 1 Available applications

Category	Application Type
Windows Server	Windows XP
	Windows Server
	Windows Performance Counter
Unix Server	AIX UNIX
	FreeBSD
	OpenBSD
	HP-UX
	Solaris
	MAC OS
	SCO Unix
	AS400
Linux server	Linux
	Kylin
	Rocky
Database server	MySQL
	Oracle
	MS SQL
	Sybase
	IBM DB2
	PostgreSQL
	Informix
	Oracle ASM
	DM
	Cache
	Database Query
	xugu
	MongoDB
	MemCached
Application server	Microsoft .NET
	JBoss
	Tomcat
	WebLogic
	Oracle AS
	WebSphere
	GlassFish
	Lotus Domino
	Lync 2010
	Lync 2013
	Jetty
	Domino Server Authentication Application Monitor
Web server	Apache
	IIS
	Nginx
	PHP
Mail server	Exchange2003
	Exchange2007
	Exchange2010
	Exchange2013
	SMTP, POP3 mail server
Middleware	Office SharePoint 2007
	Office SharePoint 2010
	Office SharePoint 2013
	WebSphere MQ
	Active MQ
	TongLINK/Q
	Oracle GoldenGate
	Hadoop
	RabbitMQ
HTTP service	URL monitor
HTTP service	URL Sequence
WEB service	SOAP
WEB service	REST
LDAP service	ActiveDirectory
LDAP service	Common LDAP
File system	File
File system	Directory
Common Services	SNMP
	DNS
	Ping Test Monitor
	JVM
	FTP/SFTP
	TCP Port
	Ceph
	IPMI
SAP	SAP
Virtual Machine	Hyper-V
	KVM
	VMware ESX
	CAS
	Citrix Xen
	VMware vCenter Server
	FusionCompute V100R005C00SPC300
Storage	HP MSA P2000
	IBM V5000
	Huawei S3900
	IBM V7000
	HP 3PAR
	H3C P5730
	EMC CLARiiON
	HW OceanStor 18500 V3

Applications monitored by APM include operating systems, databases, application servers, services, and middleware. These applications provide key services for enterprises and organizations.

After an operator adds applications to APM, APM collects monitor data and evaluates the availability and health status of the applications.

Application monitor includes common monitor and specific monitor based on the application scope. APM can monitor most mainstream network applications by using common monitor and specific monitor.

Common monitor

Use common monitor to monitor the availability and health status of one class of applications based on their common characteristics. For example, you can use POP3 and SMTP application monitors to monitor multiple email systems that provide POP3 service and SMTP service.

Specific monitor

Use specific monitor to monitor the availability and health status of one type of application based on its specific indexes. Specific monitor gets more application index data than common monitor. You can implement in-depth monitoring on applications through specific monitor, such as Exchange 2003 application monitor and Exchange 2007 application monitor.

Application monitor mode

Before APM monitors applications, make sure the APM server and the hosts where applications are deployed can reach each other.

APM monitors applications in local or remote mode.

Remote monitor

APM accesses an application to obtain monitor index data by using SSH, Telnet, SNMP, WMI, JMX, API, or JDBC, as shown in Figure 2.

Figure 2 Remote monitor

Local monitor

In this mode, you must deploy an APM agent on the host where the application is deployed. The APM agent obtains monitor index data of the application by using SSH, Telnet, SNMP, WMI, JMX, API, or JDBC. APM periodically communicates with the APM agent by using Agent messages to obtain monitor index data.

Figure 3 Local monitor

Local monitor enhances data security and can collect monitor index data that remote monitor cannot (for example, Oracle database error log files). However, local monitor supports monitoring fewer types of applications.

Monitor method

Table 2 Monitor method

Monitor method	Default port	Description
SSH/Telnet (CLI)	· TCP 23 (for Telnet) · TCP 22 (for SSH)	APM accesses the Linux or Unix OS by using Telnet or SSH, and executes commands to obtain monitor index data.
SNMP	UDP 161	Simple Network Management Protocol (SNMP) is supported by most operating systems and network devices. APM uses the SNMP agent deployed on the host to obtain monitor index data of the host. The default listening port cannot be modified.
WMI	TCP 135	Windows Management Instrumentation (WMI) is a core management technology that allows APM to collect monitor indexes from applications such as a Windows, IIS, .NET server, and AD directory.
JMX	TCP 1099	Java Management Extensions (JMX) provides a platform for managing applications, devices, and systems. APM collects Tomcat and JBoss monitor index data by using JMX.
JDBC	N/A	Java Database Connectivity (JDBC) is a Java API to execute SQL statements and provide access to multiple types of relation databases.
API	N/A	Application Programming Interface (API) includes predefined functions. APM uses the predefined functions to obtain monitor index data of applications.

APM monitor features

APM provides operators with the functions described in this section to monitor the applications.

Application monitor management

One of the functions that APM uses to monitor applications is through the application monitor management function. Once collected, the information can be displayed in different views based on your needs.

Figure 4 Application monitor and views

As shown in Figure 4, APM supports the following views:

· Application monitor—Displays the collection of application parameters and background monitor processes. Background monitor processes obtain application indexes by using the application parameters. APM periodically collects application monitor indexes by using application monitors and analyzes data based on host monitor, class monitor, and custom view.

· Host monitor—Analyzes and assesses the availability and health status of the host on which the applications run. APM provides host overview and a host monitor list.

· Class monitor—Displays the health status for each class and each application type which is predefined in APM. An application class includes one or more application types. For more information, see Table 1.

· Custom view—Allows you to customize a view as needed. You can add monitor indexes of different applications to one view to monitor indexes you focus on.

For more information, see "Monitor management."

Topology and application group management

Topology is closely related with application group management in APM.

· Topology

APM displays the physical relationship and logical relationship among applications, access devices, and physical networks in a topology. Also, APM displays the availability and health status of applications in the topology. Typically, directly related applications are used together to provides a single service. For example, a website service can use the following applications: Linux, Apache, MySQL, and PHP. These applications are related to each other and any failure among them can affect the service operation. The topology visualizes the physical relationship and logical relationship among applications, access devices, and physical networks. This is convenient for operators to promptly locate problems and evaluate affected areas to save problem-solving time.

· Application group management

Application group management allows operators to organize application monitors into several groups by function or purpose, and assign management authorities for the application monitor groups to different application administrators. Application group management simplifies the topology by displaying only the applications of the specified group rather than all applications.

For more information, see "Topology and application group management."

Agent management

In local monitor mode, an APM agent collects monitor index data from the host where the agent is deployed. APM periodically communicates with the agent by using Agent messages to obtain monitor index data.

The agent management feature allows you to manage agents deployed on hosts. You can also download, batch install, and upgrade APM agents. For more information, see "APM agent management."

Configuration management

The APM configuration management functions allow you to manage the activated alarm conditions, ports, probes, and system parameters.

· Threshold Management—Allows you to configure index value thresholds that, once reached, trigger a related alarm in the Alarm module of the IMC platform. You can configure the index name, Level-1 thresholds, and Level-2 thresholds.

· Baseline Configuration—Allows you to enable baseline function for an index and configure alarms levels. APM calculates index data in the most recent week of an index to obtain the baseline value. If the baseline function is enabled for an index and the baseline value is reached, APM triggers an alarm in the Alarm module of the IMC platform.

· Port Configuration—Allows you to configure the application monitor port and traffic statistics port of an application. APM uses the application monitor port to monitor an application in remote monitor mode, and uses the traffic statistics port to collect traffic statistics. The traffic statistics port is also used by applications to provide services.

· Probe Configuration—Allows you to configure probes for APM to periodically collect application data and displays the data in monitor reports. Probe refers to a server where the probe application is deployed. Probe analyzes traffic of applications together with the mirroring function based on the application's IP address or the combination of IP address and port. You can configure the IP address and authentication password of a probe.

· Parameter Configuration—Allows you to configure APM system parameters. You can configure the lifetime for various types of data and the color RGB value indicating alarm level.

· Template Configuration—Allows you to configure the agent and application templates. These templates enable you to install agents and add application monitors in a simplified way. You can configure host information used for agent installation in an agent template, and configure application access parameters used for adding an application monitor.

For more information, see "Configuration management."

Widget management

To facilitate administrator use, APM provides the following types of Widget functions:

· Application Topology—Displays applications, hosts, access devices, physical networks, and their relationships in a topology.

· Application Monitor—Monitors application availability and health status based on performance indexes.

· Host Monitor—Monitors operating system availability and health status for the host on which an application runs.

For more information, see "Application data display."

Application management report

IMC can generate reports based on application management report templates provided by APM. APM provides the following templates:

· Health status report—Displays the health status of applications monitored by APM.

· Availability report—Displays the availability statistics of applications monitored by APM.

IMC can generate realtime reports and scheduled reports based on the templates. Realtime reports are available to operators at any time. Scheduled reports can be emailed to operators for archiving. For more information about the report function of the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

Quick start

When you use APM for the first time, read this chapter to obtain necessary guidelines.

Accessing APM

IMC provides the following APM access modes:

· Classic—Log in to the classic IMC interface (default access mode). You can access APM functions through the navigation menu.

· Desktop—Log in to the Web desktop. You can add APM functions to the Web desktop as applications, and then click the application icons to use APM functions.

You can select the access mode on the IMC login page or on the upper right of an IMC operation page. This guide describes APM functions in classic mode.

Classic mode

In classic mode, you can access APM functions through the navigation menu. APM provides a breadcrumb navigation menu and a navigation tree, which have the same navigation menu options (see "APM navigation menu options").

· Breadcrumb navigation menu—Point to a menu option to display the submenu.

· Navigation tree—Click a menu option to display the submenu.

Unless otherwise stated, operation procedures in this guide use the navigation tree.

Breadcrumb navigation menu

As shown in Figure 5, the APM breadcrumb navigation menu has two levels.

Figure 5 Breadcrumb navigation menu

APM navigation tree

Figure 6 shows the APM navigation tree.

To expand the navigation menu:

1. Click the Resource tab.

2. From the navigation tree, click Application Manager.

Figure 6 APM navigation tree

APM navigation menu options

Table 3 APM navigation menu options

Item	Function
Quick Start	Displays the quick start page that provides operation links for auto discovery, adding applications, and application monitors. You can click these links to quickly add application monitors.
Custom View	Displays the custom view page. You can view, add, modify, and delete custom views on the page. Also, you can view custom view reports.
Application Monitor	Displays the application monitor page. You can query, add, modify, and delete application monitors on the page. Also, you can view application monitor reports.
Application Topology	Displays the application topology window. You can view the connection relationship between applications, hosts, access devices, and physical networks. Also, you can view dependencies between applications, health status of applications and hosts, and availability of applications and hosts.
Host Monitor	Displays the host monitor page. This page includes the Host tab and List tab. By default, the Host tab is displayed. · The Host tab displays the health status and availability of applications running on all hosts. · The List tab displays the CPU usage, memory usage, availability, and health status of operating systems on all hosts.
Class Monitor	Displays the class monitor page. You can view the health status and availability of each application type on this page. An application type includes multiple applications. The health status of an application type is determined by the worst health status of all applications.
Application Group	Displays the application group page. You can view, add, modify, and delete application groups on this page. Point to the Expand icon to view the application group shortcut menu.
Add Application	Displays the page for adding applications. It is the shortcut menu for adding applications on the application monitor page.
Auto Discovery	Displays the auto discovery page. Operators who use APM for the first time can quickly add applications by using the auto discovery function.
Agent Management	Displays the agent management page. You can download, install, and delete APM agents on this page.
Configurations	Displays the Configurations page. Configuration management includes the following contents: · Threshold Configuration—Allows you to manage the default threshold configuration for application monitor indexes. · Baseline Configuration—Allows you to manage baseline configuration for application monitor indexes. · Port Configuration—Allows you to manage the default mappings between applications and application monitor ports, as well as traffic statistics ports. · Probe Configuration—Allows you to view, add, modify, and remove probes. · Parameter Configuration—Allows you to manage APM service parameters. · Template Configuration—Allows you to manage application templates and APM agent templates.

Desktop mode

Figure 7 shows the APM desktop version. You can click Add application to add applications to APM.

Figure 7 Web desktop

Table 4 shows the supported APM applications.

Table 4 Supported APM applications

Item	Function
Quick Start	Displays the quick start page that provides operation links for auto discovery, adding applications, and application monitors. You can click these links to quickly add application monitors.
Custom View	Allows you to view, add, modify, and delete custom views on the page. Also, you can view custom view reports.
Application Monitor	Allows you to query, add, modify, and delete application monitors. Also, you can view application monitor reports.
Application Topology	Allows you to view the application topology and perform operations on the topology.
Host Monitor	Allows you to view host information. This page includes the Host tab and List tab. By default, the Host tab is displayed. · The Host tab displays the health status and availability of applications running on all hosts. · The List tab displays the CPU usage, memory usage, availability, and health status of operating systems on all hosts.
Class Monitor	Allows you to view the health status and availability of each application type.
Application Group	Allows you to view, add, modify, and delete application groups.
Add Application	Allows you to add application monitors.
Auto Discovery	Automatically discovers applications on the network.
Agent Management	Allows you to download, install, and delete APM agents.
Configurations	Configuration management includes the following contents: · Threshold Configuration—Manage the default threshold configuration for application monitor indexes. · Baseline Configuration—Manage baseline configuration for application monitor indexes. · Port Configuration—Manage the default mappings between applications and application monitor ports as well as traffic statistics ports. · Probe Configuration—View, add, modify, and remove probes. · Parameter Configuration—Manage APM service parameters. · Template Configuration—Manage application templates and APM agent templates.

APM perspectives

You can access APM from the following perspectives:

· Default Perspective—Log in to IMC in classic mode, or select the Default Perspective from the perspectives menu after you log in to IMC. For more information about the classic mode, see Classic mode.

· Desktop View—Log in to IMC in desktop mode, or select the Default Perspective from the perspectives menu after you log in to IMC. For more information about the desktop mode, see Desktop mode.

· Application Manager Perspective—In this perspective, IMC displays only APM related functions, including application management, topology, alarm, device management, and system management functions. Other components and part of the IMC PLAT functions are not displayed.

· Tenant Self Maintenance Perspective—In this perspective, IMC displays functions that are available to tenants according to the configured tenant privileges.

Application manager perspective

To open the application manager perspective:

1. Log in to the classic IMC interface.

2. Click the perspective switching icon , and then select the Application Manager Perspective from the popup menu.

Figure 8 Application manager perspective

Tenant self maintenance perspective

To open the tenant self maintenance perspective:

1. Log in to the classic IMC interface.

2. Click the perspective switching icon , and then select the Tenant Self Maintenance Perspective from the popup menu.

Figure 9 Tenant self maintenance perspective

Quick start guidelines

APM can monitor applications in remote or local mode.

Remote monitor

To monitor applications in remote mode, APM must access the network to obtain application index data. Operators can use APM to quickly monitor applications on the network by following the flow as shown in Figure 10.

Figure 10 Remote monitor flowchart

Preparations

Before you monitor an application, complete the following tasks:

1. Obtain general information related to the target application. General information includes:

¡ Application type

¡ Host IP address of the application

¡ Dependencies with other applications

¡ Telephone number, email, and other contact information for the administrators who manage the application

2. Add the host on which the target application resides to the IMC platform. For more information, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

3. Complete necessary configuration if the target application is of any of the following types:

¡ JBoss Server

¡ Apache Server

¡ Tomcat AS Server

¡ WebLogic AS Server (8.1)

¡ Oracle AS Server

¡ Java Runtime

¡ SAP

Auto Discovery

Using Auto Discovery, APM automatically detects applications running on the target hosts and adds application monitors. Adding application monitors through Auto Discovery includes the following phases:

· Application discovery phase—APM detects applications running on the target hosts based on port-to-application mappings.

· Adding application monitor phase—Operators add application monitors to APM based on the auto discovery result.

Not all applications supported by APM can be detected. To monitor an application that cannot be automatically detected, manually add the application to APM (see "Adding an application"). To detect applications correctly, you can modify the mappings between applications and application monitor ports in port configuration (see "Configuration management").

Table 5 provides the applications that can be automatically detected and their default application monitor ports.

Table 5 Applications that can be automatically detected in remote monitor mode

Class	Type	Application monitor port
Windows Server Monitor	Windows	TCP-135
Unix Server Monitor	AIX	· TCP-22 (SSH) · TCP-23 (Telnet)
	FreeBSD	· TCP-22 (SSH) · TCP-23 (Telnet)
	OpenBSD	· TCP-22 (SSH) · TCP-23 (Telnet)
	HP-UX	· TCP-22 (SSH) · TCP-23 (Telnet)
	SCO UNIX	· TCP-22 (SSH) · TCP-23 (Telnet)
	Solaris	· TCP-22 (SSH) · TCP-23 (Telnet)
	Mac OS	· TCP-22 (SSH) · TCP-23 (Telnet)
Linux Server Monitor	Linux	· TCP-22 (SSH) · TCP-23 (Telnet)
Database Server Monitor	SQL Server	TCP-1433
	MySQL	TCP-3306
	Oracle	TCP-1521
	DB2	TCP-50000
	DBQuery	TCP-50000
	Informix	TCP-9088
	PostgreSQL	TCP-5432
	Sybase	TCP-5000
Application Server Monitor	.NET Server	TCP-135
	JBoss Server	TCP-1099
	Tomcat Server	TCP-1099
	Lync 2010 Server	TCP-135
	Lync 2013 Server	TCP-135
	Glassfish Server	TCP-8686
	Jetty Server	TCP-8443
	Lotus Domino Server	TCP-63148
	Oracle Application Server	TCP-8888
	WebLogic Server	TCP-7001
	WebSphere Server	TCP-8880
Web Server Monitor	Apache Server	TCP-80
	IIS Server	TCP-80
	PHP	TCP-80
Mail Server Monitor	Exchange 2003	TCP-135
	Exchange 2007	TCP-135
	Exchange 2010	TCP-135
	POP3	TCP-110
	SMTP	TCP-25
Middleware Monitor	Office SharePoint 2007	TCP-135
	Office SharePoint 2010	TCP-135
	Office SharePoint 2013	TCP-135
	Active MQ	TCP-1199
	WebSphere MQ	TCP-1414
HTTP Service Monitor	URL	TCP-80
LDAP Service Monitor	Active Directory	TCP-135
LDAP Service Monitor	LDAP Service	TCP-389
Service Monitor	SNMP	UDP-161
	FTP	TCP-21
	SFTP	TCP-22
	DNS	TCP-53
	Java Runtime	TCP-1099
Storage device monitor	HP MSA P2000	TCP-5989

To use auto discovery to add an application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Auto Discovery.

The Application Discovery page opens.

3. Click Add.

The Select Devices dialog box opens.

You can locate target hosts by clicking the By View or Advanced tab. For information about selecting devices, see "Selecting devices."

4. Click Start on the Application Discovery page.

APM starts detecting the applications running on the selected hosts and displays the detection result list.

It might take a long time if APM detects multiple target hosts. To finish the automatic detection, click End during the application detection.

5. In the detection result list, click Add to Monitor of the application you want to monitor, and then set application monitor parameters.

6. Click OK.

Adding an application

Perform this task to add applications to APM that cannot be detected through auto discovery.

To add an application:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Add Application.

3. Click the type link for the target application.

4. Set application monitor parameters.

5. Click OK.

Application monitor

APM obtains application index data at an interval and displays data in a monitor report or custom view report for operators. Operators can set alarm thresholds and enable the data baseline function based on the collected data as needed.

If IMC SHM is also deployed on the APM server, operators can use the index data obtained by APM to generate SLA in SHM.

Local monitor

To monitor applications in local mode, APM must obtain application index data by using an APM agent. Figure 11 shows the local monitor flowchart.

Figure 11 Local monitor flowchart

Preparations

Before you monitor an application, complete the following tasks:

1. Verify that an APM agent can obtain data of the application to be monitored.

Table 6 Applications that can be monitored by an APM agent

Class	Type	Remarks
Windows Server Monitor	Windows	The following operating systems are supported: · Windows XP · Windows Server 2003 · Windows Server 2008 · Windows Server 2012
Windows Server Monitor	Windows Performance Counter	N/A
Linux Server Monitor	Linux	Red Hat
Database Server Monitor	SQL Server	SQL Server 2000/2005/2008
	MySQL	MySQL 5.x
	Oracle	Oracle Database 8.x/9i/10g/11g
	DB2	DB2/NT 8.2.0
	PostgreSQL	PostgreSQL 9.3.1
	Sybase	Sybase Adaptive Server Enterprise 12.5.2 and later versions
Application Server Monitor	.NET Server	All versions
	JBoss Server	JBoss Application Server 4.x/5.0.1
	Tomcat Server	Tomcat 5.x/6.x/7.0
	Lync 2010 Server	Lync Server 2010
	Glassfish Server	GlassFish 3.x
	Jetty Server	Jetty 9.0.5
	Lotus Domino Server	Lotus Domino 9.x
	WebLogic Server	WebLogic 9.x/10.x
Web Server Monitor	IIS Server	IIS 6.0
Mail Server Monitor	Exchange 2003	Exchange 2003
	Exchange 2007	Exchange 2007
	Exchange 2010	Exchange 2010
Middleware Monitor	Office SharePoint	Office SharePoint 2007
Middleware Monitor	Active MQ	ActiveMQ 5.8.0
LDAP Service Monitor	Active Directory	Active directory deployed on Windows Server 2003/2008
File/Directory Monitor	File	N/A
File/Directory Monitor	Directory	N/A
Service Monitor	Java Runtime	N/A
Virtual Device Monitor	Hyper-V	Hyper-V 2012
Virtual Device Monitor	KVM	KVM 0.9.3

2. Obtain general information related to the target application. General information includes:

¡ Application type

¡ Host IP address of the application

¡ Dependencies with other applications

¡ Telephone number, email, and other contact information for the administrators who manage the application

3. Complete the necessary configuration if the target application is Tomcat AS Server or Java Runtime.

Installing an APM agent

Operators can install an APM agent on a target host locally or remotely. APM agents can be deployed only on Windows and Linux.

Auto discovery

Auto discovery in local monitor mode takes effect only on hosts where an APM agent is deployed.

The APM agent automatically locates applications when it starts up and reports the discovery result to the APM server.

Adding an application

Operators can view the auto discovery results reported by APM agents and add applications to APM as needed.

Application monitor

If IMC SHM is also deployed on the APM server, operators can use the index data obtained by APM to generate SLA in SHM.

Quick service process

The quick service process provides a quick guide to use APM.

To open the quick service process view:

1. Select Quick Service Process from the View list in the top right corner of the IMC home page.

2. In the Select Template Category area, select Application Manager.

The quick service process view for APM opens, as shown in Figure 12.

Figure 12 Quick service process

The page includes the following areas:

¡ Application Monitoring—Click Start to monitor an application. You can also click the icons in this area to add an application monitor.

¡ Monitor Management—Click an icon to manage application monitors.

Application monitor report

After adding an application monitor to the monitoring list, APM collects and analyzes the monitored application indexes, and displays the index and performance data in a monitoring report.

Viewing the monitoring report

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

All application monitors are displayed on the Application Monitor page.

3. Click the name of the desired application monitor.

APM displays the monitoring report. The report will be updated at the polling interval configured when the application monitor was added.

The following example is a monitoring report of the Windows application monitor. Fields on the monitoring report vary by application type.

Figure 13 Windows application monitor report

Pie chart

The pie chart shows the proportion of application availability states. Point to a section of the pie chart to view the percentage of each availability state, as shown in Figure 14.

Figure 14 Pie chart

Dashboard

Typically, the dashboard shows CPU or memory indexes. Data in the middle of the dashboard is collected from the most recent APM poll of the application, as shown in Figure 15. You can click the Dashboard icon to switch to the trend graph.

Figure 15 Dashboard

Trend graph

Typically, the trend graph shows the change trend of indexes in the last hour. Point to a time to view the data from that period, as shown in Figure 16. When the trend graph shows the change trend for multiple indexes, you can click an index legend name to hide the change trend for the index.

Figure 16 Trend graph

Horizontal bar chart

The horizontal bar chart shows the disk or file system index. Point to the horizontal bar chart to view the disk usage collected when APM most recently polled the application, as shown in Figure 17.

Figure 17 Horizontal bar chart

List

The list shows multiple indexes for processes and services. Typically, a maximum of 10 entries are displayed in a list by default. To view more entries, click More, as shown in Figure 18.

Figure 18 List

Icons

· Refresh

Click the Refresh icon to refresh data in the report. By default, the report displays data collected when APM most recently polled the application. To prevent data from being frequently refreshed, the icon disappears for several seconds after you click it.

· Refresh icon in a specific area

Click the Refresh icon to refresh data in the area.

· Health State

Click the Health State icon to view the health status of the application. By default, the report shows the health status of the application collected when APM most recently polled the application. For more information about the health status, see "Monitor management."

· Weekly History

Click the Weekly History icon to view availability statistics of the application in the most recent 7 days. The data is collected hourly. You can point to the chart to view the percentage of availability states for a specific time period.

Figure 19 Weekly History

· Monthly History

Click the Monthly History icon to view availability statistics of the application in the most recent 30 days. The data is collected daily. You can point to the chart to view the percentage of availability states on a specific day.

Figure 20 Monthly History

· Set Threshold

Click the Set Threshold icon to set alarm thresholds for the application, as shown in Figure 21. When the specified threshold is reached, APM generates an alarm. For information about configuring alarm thresholds, see "Configuration management."

Figure 21 Set Threshold

· History Record

Click the History Record icon to view the history trend of the application in a line graph. The time range can be Last 1 Hour , Last 6 Hours , Today , Yesterday , This Week , This Month , or This Year .

¡ Data for the last 1 hour, the last 6 hours, and today are collected at the polling interval. Figure 22 shows the trend for the last 1 hour.

¡ Data for yesterday, this week, and this month are collected hourly. The graph also displays the maximum, minimum, and average values. Figure 23 shows yesterday's trend.

¡ Data for this year is collected daily. The statistics graph also displays the maximum, minimum, and average values. Figure 24 shows this year's trend.

Figure 22 Trend for the last 1 hour

Figure 23 Trend for yesterday

Figure 24 Trend for this year

· Time range of the trend graph

To set the time range for the trend graph, click the Last 1 Hour icon , Last 6 Hours icon , Today icon , Yesterday icon , This Week icon , This Month icon , or This Year icon .

· Dashboard/Trend graph

Click the Dashboard icon or the Trend Graph icon to display index data in a dashboard or trend graph.

· Configure

Click the Configure icon to configure indexes to be monitored. APM obtains monitored index data when APM polls the application next time. Typically, the Configure icon is located in the Process or Service area.

Common operations

Common APM operations include the following:

· Selecting devices

· Sorting a list

These operations are also applicable to other IMC components.

Selecting devices

Use this function to select hosts running applications so that APM can perform auto discovery and add application monitors. From the Select Devices window, you can filter hosts by view or advanced query.

Figure 25 Selecting devices

Filtering devices by view

1. In the Query Conditions area, click the By View tab.

2. Click the Expand icon to the left of the IP view, device view, or custom view, and then select a subview.

All devices in the subview are displayed in the Devices Found area.

Filtering devices by advanced query

1. In the Query Conditions area, click the Advanced tab.

2. Specify one or more of the following query criteria:

¡ Device IP—Enter an IPv4 or IPv6 address of the device.

If Exact Query is selected, enter a complete IPv4 or IPv6 address.

If Exact Query is not selected, enter a partial or complete IPv4 or IPv6 address. For example, if you enter 192.168, all devices whose IP addresses contain 192.168 are queried.

¡ Device IP List—Specify multiple IP addresses to be queried.

Click the Device IP List Configuration icon . The Device IP List Configuration window opens. Enter one or multiple device IP addresses in the Input Device IP field, and then click Add to add the entered IP addresses to the Device IP List field. (To enter multiple IP addresses, enter one IP address on each line.) Repeat the steps above to add all device IP addresses to be queried. To delete an IP address in the Device IP List field, select the IP address and then click Delete. Click OK to complete the operation. Make sure the device IP addresses to be queried have been added to the Device IP List field. To clear the Device IP List field, click the Clear icon .

¡ Device Label—Enter a partial or complete device label. For example, if you enter db, all devices with device labels that contain db are queried.

¡ Device Status—Select a device state from the list.

¡ Device Category—Select a device type from the list.

¡ Device Series—Select a device series from the list.

¡ Contact—Enter partial or complete contact information for the devices. For example, if you enter Bob, all devices with contact information that contains Bob are queried.

¡ Location—Enter partial or complete location information for the devices. For example, if you enter lab, all devices with location information that contains lab are queried.

¡ Device Reachability—Select a reachability state from the list: Reachable or Unreachable.

Empty fields are ignored.

3. Click Query.

All matching devices are displayed in the Devices Found area.

Selecting devices

1. Add devices to the Selected Devices area.

¡ To add one or more devices, select the devices in the Devices Found area, and then click the Add icon .

¡ To add all devices, click the Add all icon .

2. Remove undesired devices from the Selected Devices area.

¡ To remove one or more devices, select the devices in the Selected Devices area, and then click the Remove icon .

¡ To remove all devices, click the Remove all icon .

3. Click OK.

NOTE:

If only one device is found, the window does not include the Add all icon and the Remove all icon .

Sorting a list

If a list contains a large number of items (as shown in Figure 26), use the following aids to navigate the list:

· Select 8, 15, 50, 100, or 200 at the lower right of the list to set the number of items you want to display per page.

· Click the Next Page icon to page forward in the list.

· Click the Last Page icon to page forward to the end of the list.

· Click the Previous Page icon to page backward in the list.

· Click the First Page icon to page backward to the beginning of the list.

· Click a page number to display the specified page.

If the list contains more than 10 pages, click a large page number to display the remaining page numbers. For example, click page 8 to display page 11 and the rest.

Figure 26 Application monitor list

If a list contains a large number of fields (as shown in Figure 27), you can sort a list by every field that contains a Sort icon in the column label:

· When the list is sorted by a field in ascending order, the column label of the selected field is blue and contains an Ascending icon .

· When the list is sorted by a field in descending order, the column label of the selected field is blue and contains a Descending icon .

Figure 27 Sorting an application monitor list

Monitor management

Monitor management in APM allows you to collect performance indexes, health statuses, and availability of applications, and provides analysis and statistics reports based on this information in various views. Important concepts and terms in monitor management include:

· Monitor—Employs a background program to collect application index data by using a set of access parameters and to analyze the health status and availability for the application.

· Host monitor—Organizes applications by host and displays the availability and the health status of each application.

· Class monitor—Organizes applications by class and type and displays the health status of each application type.

· Custom View—Displays the performance and health status of monitored applications.

Application monitor

All monitors in APM are defined as application monitors. APM provides the ability to query, add, modify, and delete the application monitors, as well as the ability to customize the application monitor list, manage/unmanage an application monitor, poll the monitored applications, and view associated applications and root cause analysis.

You can view the management status, availability, health status, and traffic statistics of applications through the application monitor list.

An application monitor has the following statuses:

· Management status—Whether APM attempts to collect monitor indexes from the target application. The state can be Managed or Unmanaged. For applications in Managed state, APM attempts to collect their monitor indexes in each polling period. For applications in Unmanaged state, APM does not collect their monitor indexes. By default, the management status of an application is Managed.

· Availability—State of the connection between the target application and APM. States include:

¡ Available—APM can connect with the target application and collect the specified monitored indexes.

¡ Inaccessible—APM can connect with the target application but cannot collect the specified monitored indexes. This status can trigger a critical alarm.

¡ Unavailable—APM cannot connect with the target application. This status can trigger a critical alarm.

¡ Unmanaged—The target application is not monitored by APM. If the management state is Unmanaged, the availability of the application also becomes Unmanaged.

· Health Status—Evaluation result of the target application. By default, the states include:

¡ Healthy—The application is available and all indexes collected by APM do not meet the condition of a Level-1 threshold.

¡ Minor—The application is available but APM cannot collect partial monitored indexes. This health status can trigger a minor alarm.

¡ Major—The application is available and the monitored indexes collected by APM meet the condition of a Level-1 threshold. This health status can trigger a major alarm.

¡ Critical—The application is available and the monitored indexes collected by APM meet the condition of a Level-2 threshold, or the application is unavailable. This health status can trigger a critical alarm.

¡ Unknown—The application is inaccessible or unmanaged. This health status is represented by two consecutive hyphens (--) in APM.

You can modify the alarm severity level for the Level-1 Threshold Alarm of Application Management and Level-1 Threshold Alarm of Application Management traps. APM will send related alarms and calculate the health status according to the modified alarm severity levels. To modify the alarm severity level, navigate to Trap Management > Trap Definition of the IMC PLAT. For more information, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

Table 7 Relationship among management state, availability, and health status

Management status	Availability	Health status
Managed	Available	Healthy
		Minor
		Major
		Critical
	Unavailable	Critical
	Inaccessible	Unknown
Unmanaged	Unmanaged	Unknown

Viewing the application monitor list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors. Information on the list was obtained when APM last polled the monitored applications.

Application monitor list contents

¡ Name—Name of the application monitor. Click the name to view the monitoring report for the monitored application.

¡ Application Type—Type of the monitored application. Click the link for the application type to filter out other types of monitored applications. For more information about application type management, see "Application Manager overview."

¡ Host—IP address of the host on which the monitored application resides. This field is not displayed by default.

¡ Agent Collection—Use the APM agent to collect application index data. This field is not displayed by default.

¡ Speed (bps)—Total receiving and sending rate of the application, in bps. Point to the icon to view the historical records of Rx (bps) and Tx (bps). This field is displayed only when probes are configured for APM. For information about configuring probes, see "Configuration management."

¡ Rx (bps)—Receiving rate of the application, in bps. This field is not displayed by default.

¡ Tx (bps)—Sending rate of the application, in bps. This field is not displayed by default.

¡ Traffic (H)—Total traffic received and sent by the application in the last hour. This field is not displayed by default.

¡ In Traffic (H)—Traffic received by the application in the last hour. This field is not displayed by default.

¡ Out Traffic (H)—Traffic sent by the application in the last hour. This field is not displayed by default.

¡ Traffic (D)—Total traffic received and sent by the application today. This field is not displayed by default.

¡ In Traffic (D)—Traffic received by the application today. This field is not displayed by default.

¡ Out Traffic (D)—Traffic sent by the application today. This field is not displayed by default.

¡ Description—Description about the application monitor.

¡ Availability—Availability of the application. The availability can be (Available), (Unavailable), (Inaccessible), or (Unmanaged). Point to the icon to view the application availability represented by different colors for the last hour.

¡ Health—Health status of the application. The health status can be (Healthy), (Minor), (Major), (Critical), or (Unknown). Point to the icon to view the application health status represented by different colors in the last hour.

¡ Dependency Topology—Click the Dependency Topology icon to view dependencies between the application and other applications in a topology view. This field is not displayed by default. For more information about the dependency topology, see "Topology and application group management."

¡ Status—Management status of the application, which can be Managed or Unmanaged.

¡ Association—Click the Association icon to view applications associated with the application monitor. This field is displayed only when the application is a Windows operating system that is monitored through WMI. For more information, see "Viewing associated applications."

¡ Analyze—Click the Analyze icon to view the causes for the unhealthy status of an application. For more information about root cause analysis, see "Viewing root cause analysis."

¡ Contact—Contact information of the application administrator. This field is not displayed by default.

¡ Restart Server—Click the Restart Server icon to restart the server where the monitored application resides. For more information, see "Restarting a server."

¡ Alarm—If the application has unrecovered alarms, this field displays the alarm icon that represents the highest severity level of the alarms. Click the alarm icon to view the alarm list for the application.

¡ Modify—Click the Modify icon to modify the parameters of the application monitor.

¡ Delete—Click the Delete icon to delete the application monitor.

3. Click Refresh to update the content of the application monitor view list.

Restarting a server

APM supports manual or automatic restarting of Linux, NeoKylin, or Windows servers. To restart a server in auto mode, APM must work with the Intelligent Policy Center module of the IMC platform.

Restarting a server in manual mode

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Restart Server icon for an application monitor.

4. In the confirmation dialog box, click OK.

Restarting a server in auto mode

1. Click the Service tab.

2. From the navigation tree, select Intelligent Policy Center > Event Configuration.

The Event Configuration page opens.

3. Add an event:

a. Click Add on the Event Configuration page.

The Add Event Configuration page opens.

b. Select Device Alarm from the Type list.

c. Click Select Alarms to select an alarm on the page that opens. In this example, select an alarm named Level-2 Threshold Alarm of Application Management.

d. Use the default value of other parameters.

4. Add a policy for the event:

a. Access the page for adding a policy. (Details not shown.)

b. Select Auto from the Execution Type list.

c. Select Restart Server as the action.

d. Click the Alarm Parameter icon and configure a mapping between the action parameter (srcIp) and the alarm parameter (<%Device IP%>).

For more information about adding a policy, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

When a threshold alarm is generated for a monitored Linux, NeoKylin, or Windows application, the server where the application resides is restarted.

Customizing the application monitor list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click Custom Page.

The Custom Column page opens.

Customizable columns include:

¡ Name (Default)

¡ Type of application (Default)

¡ Host

¡ Agent Collection (Default)

¡ Speed (bps) (Default)

¡ Rx (bps)

¡ Tx (bps)

¡ Traffic (H) (Default)

¡ In Traffic (H)

¡ Out Traffic (H)

¡ Traffic (D) (Default)

¡ In Traffic (D)

¡ Out Traffic (D)

¡ Description

¡ Availability (Default)

¡ Health (Default)

¡ Dependency Topology

¡ Status (Default)

¡ Associate (Default)

¡ Analysis

¡ Contact

The speed, Rx, Tx, and traffic columns are displayed only when probes are configured for APM. For information about configuring probes, see "Configuration management."

4. Select the columns you want to display in the application monitor list.

5. Click the Move Up icon or Move Down icon to modify the rank of the columns in the application monitor list.

6. Click Reset if you want to restore the default columns and rank of the application monitor list.

7. Click OK.

Viewing associated applications

When a Windows application is monitored through WMI or by using an APM agent, APM automatically detects all unmonitored applications that are deployed on the Windows application. Operators can view these associated applications for the Windows application monitor.

To view associates applications:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Association icon for the Windows application monitor for which you want to view the associated applications.

The Result list page displays all unmonitored applications that are associated with the Windows application monitor.

Result list contents

¡ Device—IP address of the host on which the monitored Windows application is located.

¡ Device Name—Host name of the Windows OS.

¡ Application Type—Type of the application that is associated with the monitored Windows application and not monitored by APM.

¡ Application Monitor Port—Port through which the Auto Discovery function detects the application.

¡ Add to Monitor—Click Add to Monitor to add an application monitor for the associated application.

4. Click Back to return to the application monitor list page.

Viewing root cause analysis

APM provides the root cause analysis function to analyze the health status of applications based on application monitor indexes. The root cause analysis function is available only to applications that are not healthy.

To view root cause analysis:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The Application Monitor list page displays all application monitors.

3. Click the Analyze icon for the target application monitor.

The root cause analysis page opens, as shown in Figure 28.

Figure 28 Root cause analysis

4. Expand application index nodes to view the causes.

5. Click Close.

Querying application monitors

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Enter the complete or part of the application monitor name in the query area, and then click the Query icon located to the right of the query area.

All matching application monitors are displayed. To filter application monitors by using more filter criteria, click the Expand icon to expand the query criteria panel.

4. Set the appropriate query criteria:

¡ Name (supports fuzzy querying)

¡ Application type

¡ Availability

¡ Health status

¡ Application group

¡ Host (host IP address)

¡ Agent Collection

5. Click Query.

All application monitors that match the query condition are displayed in the application monitor list. You can click an application type on the list to filter that type of monitored applications.

6. To restore the complete application monitor list, click Reset.

Adding an application monitor

APM detects most applications through auto-discovery, except file and directory applications and those using different listening ports than most applications of the same type. To monitor undetected applications, you can manually add application monitors for them.

To add an application monitor manually:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click Add, and then select the type of the application you want to monitor.

4. Set the parameters of the application monitor, which vary with application types.

For information about setting the application monitor parameters, see the description of adding an application monitor for each type of applications.

5. Click OK.

Modifying an application monitor

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Modify icon for the application monitor you want to modify.

4. Modify the parameters of the application monitor, which vary with application types.

For more information about modifying the application monitor parameters, see the description of modifying an application monitor for each type of application. You cannot modify the application type or the IP address.

5. Click OK.

Deleting application monitors

When an application monitor is deleted, all of the associated monitor index data for that application monitor instance is deleted. You can delete any of the application monitors in APM with the exception of those referenced by custom views.

To delete one or more application monitors:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Delete icon for every application monitor you want to delete. Or select target application monitors, click Delete, and confirm your operation.

Setting the management status of an application monitor

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Select the application monitors with the management status you want to change.

4. Click Unmanage to stop monitoring the selected applications or click Manage to start collecting monitor indexes from the selected applications, depending on your needs.

Start polling

If an application is set to Manage state in APM, the application monitor collects application monitor index data at the interval polling time. If the application is set to Unmanaged state, the application monitor does not collect application monitor index data at the interval polling time. The start polling function can order APM to collect the application monitor index immediately, regardless of the management status.

To start polling:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Select the application monitors with the management status you want to change.

4. Select the application monitor for which you want to start polling.

5. Click Start Polling.

Viewing the APM server details

APM supports monitoring applications by using multiple APM servers. Specify the APM server when you add an application monitor.

To view the APM server details:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click APM Server.

The page displays the following contents:

¡ IP—IP address of the APM server.

¡ Total—Total number of applications monitored by the APM server.

¡ WMI—Number of applications monitored by the APM server through WMI.

¡ CLI—Number of applications monitored by the APM server through CLI.

¡ SNMP—Number of applications monitored by the APM server through SNMP.

¡ Agent—Number of applications monitored by the APM server by using the agent.

¡ Other—Number of applications monitored by the APM server by using other methods.

4. Click a number.

The list displays the corresponding application monitors.

Importing/exporting usernames and passwords

To manage usernames and passwords of different application monitors in batches, APM supports exporting usernames and passwords to an Excel file. If the usernames and passwords in the file are changed, you can import the new usernames and passwords to APM.

Exporting usernames and passwords

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Select application monitors for which you want to export the usernames and passwords.

4. Click Export Password.

The usernames and passwords are exported to an Excel file.

You can change the usernames and passwords in the Excel file, and then save them locally.

NOTE:

· In the Excel file, you can change only usernames and passwords, as well as the key and super password if an application monitor has. Modifying other contents in the file results in import failure.

· If the application monitor does not have a username or password, the Excel file is empty.

Importing use names and passwords

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click Import Password.

The Upload Username and Password File page opens.

4. Click Select File to select an Excel file exported by using the password export function.

5. Click Upload File.

The settings to be imported are displayed.

6. Verify the settings.

7. Click Import.

NOTE:

To view the most recent import result, click View Import Result on the Import Password page. The import result is cleared when IMC restarts or you log off.

Exporting application data

APM supports exporting the application monitoring data to an Excel file.

To export application data:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Perform one of the following tasks:

¡ To export data from specific application monitors, select the application monitors, and then click Export Selected.

¡ To export data from all application monitors, click Export All.

4. Save the Excel file locally.

Importing applications

This feature allows you to batch import applications of the same type. Unsupported application types are URL Sequence, Lync 2010 server, Lync 2013 server, Exchange 2003, Exchange 2007, Exchange 2010, and Exchange 2013.

To import applications, perform the following tasks:

1. Export an import template.

2. Configure the import template.

3. Import applications.

Exporting an import template

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Import Application.

The Batch Import Application page opens.

3. Click Select next to the Application Type field.

All available application types are displayed.

4. Select an application type, and then click OK.

The Application Category and Application Type fields are automatically populated.

5. Click Export to export an import template for the selected application type and save it locally.

Configuring the import template

1. Open the locally saved import template file.

2. Configure the application information to be imported.

Each line represents an application monitor.

Table 8 contains information specific to setting configuration items in an import template for bulk adding application monitors. For more information about setting the configuration items for an application monitor, see the procedure for adding that application monitor in this document.

Some configuration items are not available in an import template, and they are configurable only when you add application monitors one by one.

Table 8 Restrictions and guidelines about configuration items

Configuration item	Remarks
Use Template	The import template does not include this item. The value for this item is Disable by default.
Related Applications	The import template does not contain this item. After applications are imported, you can navigate to Application Manager > Application Monitor to configure related applications for an application.
Detect Application	The import template does not contain this item. Application detection is enabled by default.
Monitor type template	The import template does not contain this item.
Monitor types of SSH, Telnet, and SNMP	To set the monitor type of SNMP, Telnet, or SSH in the import template: 1. Configure the access parameters in the SNMP, Telnet, or SSH sheet. 2. Copy the SNMP ID, Telnet ID, or SSH ID to the corresponding column of the app Config sheet.
Monitor type of SSH	The public key authentication method is not supported in the import template. After applications are imported, you can navigate to Application Manager > Application Monitor to configure the public key authentication method for an application.
Use IPMI	The import template does not contain this item. IPMI monitoring is disabled by default.
Windows application	When the monitor type is set to VMI, the import template does not support enabling event logging. After the application is imported, you can navigate to Application Manager > Application Monitor to configure event logging for the application.
FTP service application	The import template automatically sets the Whether to Download File and Whether to Upload File configuration items to Yes for the FTP service application. After the FTP service application is imported, you can navigate to Application Manager > Application Monitor to modify these configuration items for the application.
Windows performance counter applications	APM does not support batch importing Windows performance counter applications when it is deployed on Linux.

Importing applications

1. Open the Batch Import Application page.

2. Click Select next to the Application Type field.

All available application types are displayed.

3. Select an application type, and then click OK.

The Application Category and Application Type fields are automatically populated.

4. Click Select File to select a configured import template file.

5. Click Upload to upload the import template file.

The applications to be imported are displayed in a list.

6. Click Import All to import all applications in the list.

To stop importing the applications, click Stop All.

To clear the application list, click Clear All.

Host monitoring

Host monitoring focuses on the availability and the health status of applications on each host. You can view a host monitor in either Host mode or in List mode.

Viewing a host monitor in host mode

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Host Monitor.

The Host Monitor page displays all host monitors in the default Host mode, as shown in Figure 29. The Host mode organizes application monitors based on hosts. The background color of each monitored application stands for the health status of that application. The availability icon to the left of each application monitor name stands for the availability status of that application. For more information about the availability and health status, see "Application monitor."

3. For a host managed by IMC, click the device label of the host to view its details. For more information about viewing host details, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

4. Click an application monitor name to view the monitoring report for that application. The report contents vary with application types and will be described in subsequent chapters.

Figure 29 Host tab on the Host Monitor page

Viewing a host monitor in list mode

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Host Monitor.

The Host Monitor page displays all host monitors in the default Host mode.

3. Click the List tab.

The Host Monitor List opens, as shown in Figure 30.

Host monitor list contents

¡ Host—Device label of the host machine. For a host managed by the IMC platform, click the device label to view its details. For more information about viewing host details, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

¡ OS—Operation system used in the host machine.

¡ CPU—CPU usage of the operating system. Click the History Record icon to view the history CPU usage trend graph. Options are Last 1 Hour icon , Last 6 Hours icon , Today icon , Yesterday icon , This Week icon , This Month icon , and This Year icon .

¡ Memory—Memory usage of the operating system. Click the History Record icon to view the history memory usage trend graph. Options are Last 1 Hour icon , Last 6 Hours icon , Today icon , Yesterday icon , This Week icon , This Month icon , and This Year icon .

¡ System Running Time—Duration from the time when the OS started up to the time when APM most recently polled the OS.

¡ Availability—Availability of the operating system of the host for the last poll query. The availability is (Available), (Unavailable), (Inaccessible), or (Unmanaged). Point to the icon to view the availability represented by different colors for the last hour.

¡ Health—Health status of the operating system on the host for the last poll query. The health status is (Healthy), (Minor), (Major), (Critical), or (Unknown). Point to the icon to view the health status represented by different colors in the last hour.

¡ Host Topology—Click the Host Topology icon to view the host and related monitored applications in a topology view. For more information about the host topology, see "Topology and application group management."

¡ Analyze—Click the Analyze icon to view the root cause analysis for the application. For more information, see "Viewing root cause analysis."

¡ Application—Monitored applications on the host, except the operating system. Click an application icon to view the monitoring report for the application.

4. Click Refresh to update the content of the Host Monitor List.

Figure 30 Host monitor list

Class monitoring

Class monitoring focuses on the health status of applications. Application types are defined in APM. Every application type can have more than one application and the health status of the application depends on the worst health status.

To view application monitors by class:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Class Monitor.

The Class Monitor page displays all application monitors based on their classes and types, as shown in Figure 31. The leftmost column displays the monitor classes and other columns are application types sorted by class. The background colors stand for the health status of the application types. The overall health status depends on the worst health status.

3. Click an application class name to view the list of all application types in that class.

The numbers next to the application class name represents the number of applications in healthy state out of the total number of applications for that class.

4. Click an application type name to view the list of all applications for that type.

The numbers next to the application class name represents the number of applications in healthy state out of the total number of applications for that type.

5. Point to an application type name to view the details of the health status. For example, Healthy: 1, Critical: 0, Major: 0, Minor: 0, --: 0.

Figure 31 Class monitor

Custom views

APM allows operators to combine concerned indexes of different applications into one custom page to supply the support for the whole service performance and health status.

Viewing the custom view list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Custom View.

The Custom View List page displays all custom views.

Custom view list contents

¡ Name—Name of the custom view.

¡ Description—Details of the custom view.

¡ Monitor Report—Click the Monitor Report icon to view the custom report.

¡ Modify—Click the Modify icon to modify the custom view.

¡ Delete—Click the Delete icon to delete the custom view.

3. Click Refresh to update the content of the custom view list.

Viewing custom view details

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Custom View.

The Custom View List page displays all custom views.

3. Click the name of a custom view to view its details.

Custom view details

¡ Name—Name of the custom view.

¡ Description—Description of the custom view.

¡ Application Index List—Entire application monitor indexes for the custom view.

¡ Application Index—Application index name used by the custom view.

¡ Application Name—Name of the application to which the monitor index belongs.

¡ Application type—Type of the application to which the monitor index belongs.

3. Click Back to return to the Custom View List page.

Adding a custom view

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Custom View.

The Custom View List page displays all custom views.

3. Click Add.

The Add Custom View page opens.

4. Enter the name and description of the custom view. Description is helpful for managing and maintaining the custom view.

5. Click Add in the application index list.

The Select Application Index dialog box opens.

a. Click the Unfold icon or Fold icon to expand or collapse an application type/application monitor index. One application type can contain one or more applications under the selected type.

b. Select the appropriate application indexes for the custom view.

c. Click OK.

The selected indexes are displayed in the application index list.

6. Click the Move Up icon or Move Down icon to change the arrangement of the monitor indexes that display in the custom report.

7. Click OK.

Modifying a custom view

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Custom View.

The Custom View List page displays all custom views.

3. Click the Modify icon for the custom view you want to modify.

The Add Custom View page opens.

4. Modify the description of the custom view. Description is helpful for managing and maintaining the custom view. You cannot modify the name of the custom view.

5. Click Add in the application index list.

The Select Application Index dialog box opens.

a. Click the Unfold icon or Fold icon to expand or collapse an application type/application monitor index. One application type can contain one or more applications under the selected type.

b. Select the appropriate application indexes for the custom view.

c. Click OK.

6. Click the Delete icon for the application index that you do not want to display in the custom report, and then click OK to confirm the deletion.

7. Click the Move Up icon or Move Down icon to change the arrangement of the monitor indexes that display in the custom report.

8. Click OK.

Deleting a custom view

When you delete a custom view, the associated application monitor indexes and data are not deleted, and you can view the application monitor indexes and data for a deleted custom view through the monitor reports.

To delete a custom view:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Custom View.

The Custom View List page displays all custom views.

3. Click the Delete icon for the custom view you want to delete.

4. Click OK to confirm the deletion.

Viewing a custom view report

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Custom View.

The Custom View List page displays all custom views.

3. Click the Report icon for the custom view for which you want to view the monitoring report.

The custom view reports display different contents with each different monitor index. Different custom reports will be described in subsequent chapters.

The monitor index can set the same threshold value as that in the application monitor report. If you modify the threshold value in the custom view report, the threshold value in the application monitor report is also changed. For more information about threshold setting, see "Configuration management."

Topology and application group management

APM offers flexible topology and application group management functions:

· Topology—APM displays the physical relationship and logical relationship among applications, access devices, and physical network in a topology. Also, APM displays the availability and health status of applications in the topology.

· Application group management—Application group management allows operators to organize applications monitors into several groups by function or purpose and assign management authorities for the application monitor groups to different application administrators. Application group management simplifies the topology by displaying only the applications of the specified group rather than all applications.

Topology management

APM provides the following topology types:

· Application topology

· Dependency topology

· Host topology

· Group topology

· Converged topology

Topologies present applications, hosts, access devices, physical network, and their relationships in a graphical way to improve management efficiency.

Topology tools and right-click menu

In APM, all topologies share the same tools and provide one or more right-click menu options for the monitored applications.

Except the bird's-eye view, all tools are located on top of a topology to provide viewing aids.

Table 9 Topology tools

Tool	Description
	Enters the select mode, in which operators can select and drag nodes on the topology. This is the default mode when you enter the topology.
	Changes the mouse cursor to a magnifier to enlarge specific parts of the topology.
	Enables or disables the bird's-eye view of the application.
	Zooms in the topology.
	Zooms out the topology.
	Restores the original size of the topology.
	Fits the topology to the window.
	Generates the snapshot picture of the topology.
	Updates the topology layout.
	Hides or displays alarms of the nodes on the topology.
	Hides or displays interface numbers of the nodes on the topology.
	Saves the topology after adjustment.
	Displays the topology in a bird's-eye view, from which operators can quickly understand the general layout of the topology and locate the current screen of topology in the whole topology map. Operators can click to enable or disable the bird's-eye view of the topology.

You can quickly navigate to related functions of a monitored application by using the right-click menu options on the topology. On the application topology, the right-click menu options of an application icon also apply to hosts icons attached with an operating system logo (such as ).

Right-click menu options:

· Application Monitor—Select this option to view the monitoring report of the monitored application.

· Host Topology—Select this option to view the host topology. This option is available only for the host icon.

· Dependency Topology—Select this option to view the dependency topology of the monitored application.

· Query Alarm—Select this option to query alarms generated by the monitored application. This option is available only when the applications have alarms generated.

· Traffic Trends—Select this option to view the trends of the rates at which the monitored application received and sent traffic in the last hour.

Dependency topologies, host topologies, and group topologies support only the Monitor Application option.

Viewing an application topology

The application topology displays the physical relationship and logical relationship among applications, hosts, access devices, and physical network.

Physical relationship includes the connection relationship between access devices and the physical network, the connection relationship between hosts and access devices, and the relationship between OS applications and hosts.

Logical relationship includes the dependencies between non-OS applications and the OS and the dependencies between applications.

To view the application topology:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Topology.

The application topology window opens, as shown in Figure 32. The topology shows all applications that the current operator has the management privileges to and the relationships among the applications, related hosts, access devices, and the physical network.

Figure 32 Application topology window

Table 10 Application topology icons

Icon	Description
	Represents a host for which APM does not monitor the operating system.
	Represents a host for which APM is monitoring the operating system. The logo attached to the host icon varies with operating systems.
	Represents an application monitored by APM. The icon varies with the application type. This icon indicates an Active Directory application.
	This icon contains the following information: · Alarm—Number and highest severity of unrecovered alarms for an application. This icon is not displayed if no unrecovered alarm exists for the application. · Availability—Availability of an application for the last polling query. The icon varies with the availability. For more information, see "Monitor management." · Health status—Health status of an application for the last polling query. The icon varies with the health status. For more information, see "Monitor management."
	Represents a device that provides network access for applications. To display such devices on the topology, make sure you have added them to the IMC platform as access devices.
	Represents the physical network to which an access device is connected.
	Represents dependencies between two applications that use the same IP address. A dashed line represents indirect dependencies between the applications. Indirect dependencies are generated when the current operator has no management privileges to one or more intermediate applications.
	Represents dependencies between two applications that use different IP addresses. A dashed line represents indirect dependencies between the applications. Indirect dependencies are generated when the current operator has no management privileges to one or more intermediate applications.
	Represents the connection between a host and an access device or between an access device and the physical network. For a host-to-access device connection, the port that connects the host to the access device is also displayed. A dashed line represents an indirect connection between a host and the physical network. An indirect connection is displayed when the access device is not added to the IMC platform. For information about adding devices to IMC, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

Viewing a dependency topology

A dependency topology focuses on a single application and displays its dependencies with other applications, directly or indirectly.

You can view a dependency topology by using one of the following methods:

Method 1

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Dependency Topology icon for the application for which you want to view the dependency topology.

Method 2

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of the application monitor.

The application monitor report page opens.

4. Click the Relationship icon located in the Monitor Information area for the target application.

Method 3

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Topology.

The application topology window opens.

3. Right-click the application icon, and then select Dependency Topology from the popup menu.

The dependency topology window opens, as shown in Figure 33. The dependency topology contains only application icons and lines. For the icon description, see Table 10.

Figure 33 Dependency topology window

Viewing a host topology

A host topology focuses on a single host and displays dependencies of the operating system that runs on it with other applications.

To view a host topology:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Host Monitor.

The Host Monitor page displays all host monitors in the default Host mode.

3. Click the Host tab.

The Host Monitor List is displayed.

4. Click the Host Topology icon for the host for which you want to view the host topology.

The host topology window opens, as shown in Figure 34. The host topology filters out physical networks and hosts for which APM does not monitor the operating system. For the icon description, see Table 10.

Figure 34 Host topology window

Viewing a group topology

Group topologies include logical group topology and physical group topology:

· Logical group topology—With a selected application group as the root, displays all its subgroups, applications in each subgroup, and logical relationship between the subgroups.

· Physical group topology—Displays the physical relationship and logical relationship between applications, access devices, and the physical network in a group (excluding subgroups).

Viewing a logical group topology

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Group.

The application group list page displays all application groups.

3. Click the Group Topology icon for the target application group.

The logical group topology window opens.

Figure 35 Logical group topology window

Table 11 Logical group topology icons

Icon	Description
	Represents an application monitored by APM. The icon varies with the application type. This icon indicates a Windows application.
	Represents an application group. The operator with the management authority for the application group can view all applications of the application group in the topology. For more information about application group, see "Application group management"
	The alarm icon represents the number and highest severity of unrecovered alarms for an application. This icon is not displayed if no unrecovered alarm exists for the application.
	The availability icon represents the availability of an application or application group for the last polling query. The availability of an application group is determined by the application with the worst availability in the group or its subgroup. For information about the icon to display, see "Monitor management."
	The health status icon represents the health status of an application for the last polling query. The health status of an application group is determined by the application with the worst health status in the group or its subgroup. For more information about the icon to display, see "Monitor management."
	The availability icon represents the availability of an application group. The availability of an application group is determined by the application with the worst availability in the group or its subgroup.
	The health status icon represents the health status of an application group. The health status of an application group is determined by the application with the worst health status in the group or its subgroup.
	Points to a subgroup or application that an application group contains.

Application group enables operators to manage applications by group based on the granted authorities. If an operator does not have the management authority for an application group, the operator cannot view applications of the application group in the logical group topology.

Viewing a physical group topology

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Group.

The application group list page displays all application groups.

3. Click the Physical Topology icon for the target application group. You can also click the Phy Topology tab on the Logic Topology page.

The physical group topology window opens.

Figure 36 Physical group topology

The application topology displays all applications on the network. The physical group topology displays the applications of an application group. Icons in the group topology are similar to those in the application topology. For more information about the icons, see Table 10.

The right-click menu of physical group topology includes only the Application Monitor option for you to display the application monitor report.

Viewing a converged topology

A converged topology converges multiple types of topologies into one topology. For more converged topology information, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

To view a converged topology:

1. Click the Resource tab.

2. From the navigation tree, select View Management > Network Topology.

The topology page opens.

3. From the topology navigation tree, select Converged Topology.

Figure 37 Converged topology window

Adding an application topology into a converged topology

1. On the converged topology, right-click the blank space.

2. Select Add Application from the right-click menu.

3. On the popup window, select one or more applications, and then click OK to add the applications to the converged topology.

On the converged topology that includes applications:

· If an application does not have unrecovered alarms, the color of the application icon is green. If an application has unrecovered alarms, the application icon shows a color that corresponds to the highest alarm severity level, and the background of the application icon flashes.

· Click an application icon on the converged topology to display the key monitoring indexes of the application. Different applications have different key monitoring indexes. Common monitoring indexes for applications include:

¡ Availability—Availability of the application in the last polling of APM.

¡ Health—Health of the application in the last polling of APM.

¡ Monitor Report—Click the Monitor Report link to view the application's monitor report.

· Right-click an application icon on the converged topology to open the operation menu of the application.

¡ Add Link—Click this item. On the opened window, select a node and click OK. A link will be added between the application and the node.

¡ Add to subview—Click this item. On the opened window, select a subview and click OK to add the application to the subview.

¡ Modify Label—Click this item. On the opened window, modify the application label and click OK. This operation modifies only the application label displayed on the converged topology.

¡ Delete—Click this item to delete the application from the converged topology.

Application group management

APM allows you to manage monitored applications in groups. By default, all monitored applications belong to the system default group named ungrouped and all operators can manage applications in ungrouped. Once a monitored application is assigned to an application group, the application can be managed only by operators who are granted privileges to manage that application group.

You can add four hierarchy subgroups under a parent group and there is no inheritance relationship between them. You can view, add, modify, and delete applications.

Viewing the application group list

You can view all application groups in the Application Group List.

To view the application group list:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Group.

The application group list page displays all application groups.

Application group list contents

¡ Name—Name of the application group. Click the name to view all monitored applications in the group.

¡ Availability—Availability of the application group. It is determined by the application with the worst availability in the group or its subgroup. The field value is Available when the application group does not include any applications.

¡ Health Status—Health status of the application group. It is determined by the application with the worst health status in the group or its subgroup. The field value is Healthy when the application group does not include any applications.

¡ Application Group Topology—Click the Application Group Topology icon to view the logical group topology. For more information about the group topology, see "Viewing a logical group topology."

¡ Physical Topology—Click the Physical Topology icon to view the physical group topology. For more information about the group topology, see "Viewing a physical group topology."

¡ Analyze—Click the Analyze icon to analyze the root cause for the alarms generated by applications in the group or subgroups.

Figure 38 Root cause analysis

¡ Details—Click the Details icon to view detailed information about the application group.

¡ Modify—Click the Modify icon to modify the application group.

¡ Delete—Click the Delete icon to delete the application group.

3. Click Refresh.

NOTE:

You can sort the application group list by name, availability, or health status by clicking the appropriate list label.

Viewing the application group details

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Group.

The application group list page displays all application groups.

3. Click the Details icon for the application group for which you want to view its details.

Application group details

¡ Name—Name of the application group.

¡ Description—Description of the application group.

¡ Operator Group—Names of the operator groups to manage the application group and applications in the application group. For information about viewing operators in the group, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

¡ Application—All applications that belong to the application group.

¡ Parent Group—Application group's parent group. An application group can belong to only one parent group.

4. Click Back to go back to the application list page.

Adding an application group

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Group.

The application group list page displays all application groups.

3. Click Add.

The Add page opens.

4. Specify a unique application group name.

5. Describe the application group details in the Description field.

6. Select groups of operators who are permitted to manage the application group and its member applications:

a. Click Add. The Select Operator Group window opens.

b. Select one or more operator groups as needed.

c. Click OK.

All selected operator groups are displayed in the Operator Group box.

7. Add applications to the application group:

a. Click Add. The Select Application window opens.

b. Select one or more applications as needed.

c. Click OK.

All selected applications are displayed in the Application box.

8. Select a parent group for the application group from the Parent Group list. If no parent relationship exists, leave this option blank.

9. To send alarm notifications for monitored applications:

a. Select enable from the Alarm Notification list.

b. On the Mail Setting tab, enter an IP address in the Destination IP Address field, and then click Add.

c. On the SMS Setting tab, enter a phone number in the Mobile Phone Number field, and then click Add.

d. Select an alarm level from the Concerned Alarm Levels list.

e. Select All Alarms or Selected Alarms from the Concerned Alarms list.

If Selected Alarms is selected, click Select, select alarm types to be included, and then click OK.

f. Set the time range for alarm notifications in the Time Ranges field. The time range is set by week in hh:mm-hh:mm format.

10. Click OK.

Modifying an application group

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Group.

The application group list page displays all application groups.

3. Click the Modify icon for the application group you want to modify.

4. Enter a unique new name for the application in the Name field.

5. Modify the description of the application group in the Description field.

6. Modify the groups of operator who are permitted to manage the operator group and its member applications:

a. Click Add.

The Select Operator Group page opens.

b. Select one or more operator groups as needed.

c. Click OK.

All selected operator groups are displayed in the Operator Group box.

d. Select one or multiple operator groups that you no longer permit to manage the application group and its members in the Operator Group box.

e. Click Delete.

Each selected operator group is removed from the Operator Group box.

7. Modify applications in the group:

a. Click Add.

The Select Application page opens.

b. Select one or more applications as needed.

c. Click OK.

All selected applications are displayed in the Application box.

d. Select one or more applications you want to remove from the application group in the Application box.

e. Click Delete.

f. Click OK.

Each selected operator group is removed from the Application box.

8. Select a new parent group from the Parent Group list. If no parent relationship exists, select the blank option from the list.

9. To send alarm notifications for monitored applications:

a. Select enable from the Alarm Notification list.

b. On the Mail Setting tab, enter an IP address in the Destination IP Address field, and then click Add.

c. On the SMS Setting tab, enter a phone number in the Mobile Phone Number field, and then click Add.

d. Select an alarm level from the Concerned Alarm Levels list.

e. Select All Alarms or Selected Alarms from the Concerned Alarms list.

If Selected Alarms is selected, click Select, select alarm types to be included, and then click OK.

f. Set the time range for alarm notifications in the Time Ranges field. The time range is set by week in hh:mm-hh:mm format.

10. Click OK.

Deleting an application group

Use caution when deleting an application group because this action simultaneously deletes any associated subgroups. Further, once an application group is deleted, applications in the deleted group are moved to ungrouped if they do not belong to any other application groups.

To delete an application group:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Group.

The application group list page displays all application groups.

3. Click the Delete icon for the application group you want to delete.

4. Click OK.

APM agent management

An APM agent collects application index data from a target host in local monitor mode. Using an agent to collect data can secure the OS privileges and obtain data that cannot be obtained in remote monitor mode.

Installing and upgrading an APM agent

Make sure the APM agent has the same version as APM. You can install and upgrade an APM agent locally and remotely.

Installing an APM agent locally

To install an APM agent locally, operators must download the installation package (for Windows or Linux) to the local directory by using agent management.

To install an APM agent locally:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

3. Click Download.

4. Select Agent Package (Windows) or Agent Package (Linux) as needed.

The installation package is saved to the local directory.

5. Copy the installation package to the destination host by using FTP, file sharing, or SCP, and decompress it.

6. Double-click the install.bat script and enter the IP address of the IMC server as prompted.

If IMC is deployed in distributed mode, enter the IP address of the master server.

7. Click OK.

Installing an APM agent remotely

This function uses WMI (Windows) or SSH (Linux) on the destination host. To install an APM agent remotely, you must obtain the IP address of the destination host and administrator username and password.

To install an APM agent remotely:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

3. Click Install.

4. Configure the following parameters:

¡ Destination Host IP—Enter the IP address of the destination host, and then click Add. The IP address is added to the Host List area.

¡ Host List—Displays the hosts on which the agent is remotely installed. To remove an IP address from the Host List area, select the IP address, and then click Delete.

¡ Host Type—Select a host type, Windows or Linux. If you click Select Template, this field is automatically populated.

¡ Installation Path—Enter the absolute agent installation path. In this example, enter D:\agent for Windows and /home/agent for Linux. If you click Select Template, this field is automatically populated.

¡ Username/Password—Enter the username and the password used for connecting to the destination host. If you click Select Template, this field is automatically populated.

- For Windows, the username must have the administrator rights.

- For Linux, the username must have the root rights and the rights to execute the installation file.

¡ Description—Enter a description of the installation task.

5. Click Install.

Figure 39 Installing the APM agent remotely

NOTE:

To use an agent template, you must add the template to APM first. For information about adding an agent template, see "Configuration management."

Upgrading an APM agent locally

To upgrade an APM agent locally, operators must obtain the upgrade package (for Windows or Linux) by using agent management.

To upgrade an APM agent locally:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

3. Click Download.

4. Select Agent Upgrade Package (Windows) or Agent Upgrade Package (Linux) as needed.

The upgrade package is saved to the local directory.

5. Copy the upgrade package to the Agent directory of the agent installation path.

6. Extract the compressed files from the upgrade package into the current directory.

7. Run update.bat in the AgentUpdate directory.

Upgrading an APM agent remotely

This function uses WMI (Windows) or SSH (Linux) on the destination host. To upgrade an APM agent remotely, make sure WMI or SSH is enabled.

After APM is upgraded, it automatically detects all managed APM agents and pushes upgrade packages for agent upgrade. If an APM agent fails to be upgraded remotely, upgrade the agent locally. For more information, see "Upgrading an APM agent locally."

Managing APM agents

You can use agent management to install, delete, start, or stop APM agents, or automatically detect applications.

Viewing the APM agent list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

The agent list is displayed.

Agent list contents

¡ Destination Host IP—IP address of the host where the APM agent is deployed. Click the IP address to view agent details.

¡ Version—Version of the APM agent.

¡ Installation Time—Time when the APM agent was installed.

¡ Upgrade Time—Time when the APM agent was most recently upgraded.

¡ Description—Descriptive information about the APM agent.

¡ Status—Current state of the APM agent.

¡ Operation—Operations that can be performed on the APM agent.

¡ Auto Discovery—The APM agent automatically detects all applications running on the destination host after installation completion. Click Result to view the auto discovery result.

¡ Managed Application—Applications monitored by the APM agent on the destination host.

¡ Delete—Click the Delete icon to delete APM agents in incorrect status due to authentication error or connection failure.

Viewing agent details

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

The agent list is displayed.

3. Click the IP address of an APM agent to view its details.

¡ Destination Host IP—IP address of the host where the APM agent is deployed.

¡ Host Type—OS of the destination host, Windows or Linux.

¡ Installation Path—Absolute APM agent installation path. For example, D:\agent on Windows and /home/agent on Linux.

¡ Description—Descriptive information about the APM agent.

4. Click Back.

Starting an APM agent

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

The agent list is displayed.

3. Click the Start icon for an APM agent.

The APM agent status becomes Starting. The Start icon is displayed only for APM agents in Stopped state.

4. Click Refresh.

Stopping an APM agent

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

The agent list is displayed.

3. Click the Stop icon for an APM agent.

The APM agent status becomes Stopping. The Stop icon is displayed only for APM agents in Started state.

4. Click Refresh.

Viewing the auto discovery result

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

The agent list is displayed.

3. Click Result in the Auto Discovery column for an APM agent.

The Auto Discovery Result page opens.

¡ Device—IP address of the host where the APM agent is deployed.

¡ Application Type—Type of the application.

¡ Application Monitor Port—Port used to monitor the application.

¡ Add to Monitor—Click Add to Monitor for an unmonitored application to add monitor for the application. Click Add the same type of application for a monitored application to add monitor for the same type of applications.

Adding an application monitor

You can click Add to Monitor or Add the same type of application on the Auto Discovery Result page to add an application monitor.

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

The agent list is displayed.

3. Click Result in the Auto Discovery column for an APM agent.

The auto discovery result page opens.

4. Click Add to Monitor or Add the same type of application.

5. On the page that opens, configure the application monitor parameters.

The Enable Agent Collection parameter is displayed only for application that can be monitored by an APM agent.

6. Click OK.

Deleting an APM agent

This function deletes APM agents in incorrect status due to authentication error or connection failure.

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Agent Management.

The agent list is displayed.

3. Click the Delete icon for an APM agent.

4. Click OK.

Configuration management

APM provides the following additional configuration management functions:

· Threshold Management—Sets threshold alarm conditions for the monitoring application indexes. If the collected indexes meet the threshold alarm conditions, APM sends a corresponding alarm through the alarm function of the IMC platform. If the alarm notification and forwarding configuration is set correctly, operators can receive alarm information sent by APM through emails or short messages.

· Baseline Configuration—Enables or disables the baseline function for application indexes. When you enable the baseline function for an application index, APM performs the following operations:

¡ Collects the index data.

¡ Generates initial baseline data after seven days.

¡ Generates stable baseline data after five weeks.

APM determines the index state according to the baseline data. Alarms are generated when the baseline data is in an abnormal state. If the alarm notification and forwarding configuration is set correctly, operators can receive alarm information sent by APM through emails or SMS messages.

· Port Configuration—Sets default application monitor and traffic collection ports for applications. Through ports, APM can identify different applications in Auto Discovery and traffic collection.

· Probe Configuration—Manages a list of probes. A probe is a server where the probe application is installed. Operators can collect the network traffic of applications by mirroring network traffic to the probe.

· Parameter Configuration—Sets APM system parameters, including the monitor data retention periods and data background colors.

· Template Configuration—Provides application templates for application monitors and agent templates for remotely installed agents. Using templates simplifies the configuration and reduces the chances of making mistakes.

Threshold management

APM predefines multiple monitor indexes for each type of applications, and sets the threshold alarm conditions for certain key monitor indexes. Operators can view application monitor indexes configured with the threshold alarm function and their threshold configurations. To enable the threshold alarm function for other application monitor indexes, use the monitor index adding function in threshold configuration.

By default, when application monitor indexes meet Level-1 threshold conditions, APM sends major alarms. When application monitor indexes meet Level-2 threshold conditions, APM sends critical alarms. You can modify the alarm severity level for the Level-1 Threshold Alarm of Application Management and Level-2 Threshold Alarm of Application Management traps. APM will send related alarms and calculate the health status according to the modified alarm severity levels. To modify the alarm severity level, navigate to Trap Management > Trap Definition of the IMC PLAT. For more information, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

Application monitor thresholds can be global or custom, depending on the effective range. You can set a global threshold for a monitor index only in threshold configuration. You can set a custom threshold in the application monitor report or custom view report. By default, monitor indexes enabled with the threshold alarm function use global thresholds.

· Global threshold—Applies to a specific widely deployed application type. The same application type has the same global threshold.

· Custom threshold—Monitors a single application. With custom thresholds, applications of the same type can use different thresholds. You can enable and modify custom thresholds for a monitor index only after you add a global threshold for the monitor index.

This section describes how to query, add, modify, and delete alarm indexes, and how to configure monitor indexes to use global thresholds or custom thresholds in reports.

Viewing the global threshold List

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Threshold Configuration.

The Global Threshold List displays all monitor indexes enabled with the threshold alarm function and the global threshold of each index.

4. Click an application category to view monitor indexes for this application category.

The Application Type field also refreshes.

To view baseline configurations for all application categories, click Unlimited next to Application Category.

5. Click an application type to view monitor indexes for this application type.

To view baseline configurations for all application types of an application category, click the application category, and then click Unlimited next to Application Type.

Global Threshold List contents

¡ Application Type—Type of the application.

¡ Application Unit—Name of the application unit to which the monitor index belongs. Each application unit corresponds to an independent area in the application monitor report.

¡ Index—Name of the application monitor index enabled with the threshold alarm function.

¡ Threshold Condition—Threshold condition, which can be Greater than or equal to (≥), Less than or equal to (≤), Include, or Exclude.

¡ Enable Level-1 Threshold—Displays whether the Level-1 threshold for the monitor index has been set.

¡ Level-1 Threshold—Level-1 threshold value of the monitor index.

¡ Trigger Times—Number of times that the monitor index meets the Level-1 threshold to trigger an alarm.

¡ Enable Level-2 Threshold—Displays whether the Level-2 threshold for the monitor index has been set.

¡ Level-2 Threshold—Level-2 threshold value of the monitor index.

¡ Trigger Times—Number of times that the monitor index meets the Level-2 threshold to trigger an alarm.

¡ Modify—Click the Modify icon to modify the predefined or user-defined global threshold values.

¡ Delete—Click the Delete icon to delete the predefined or user-defined global threshold values.

6. Click Refresh to refresh the global threshold list.

7. Click Back to return to the Configurations page.

Adding threshold configuration

With this function, operators can manually enable the threshold alarm function and set thresholds for monitor indexes. In addition, operators can configure monitor indexes to use global thresholds or custom thresholds in the application monitor report or custom view report.

To add threshold configuration for a monitor index:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Threshold Configuration.

The Global Threshold List is displayed.

4. Click Add.

The Add Threshold page opens.

5. Configure the following parameters for the monitor index:

¡ Application Type—Click Select, and then select an application type from the popup window. The selected application type name automatically populates the Application Type field.

¡ Application Unit/Index/Threshold Type—Click Select, and then select an application monitor index from the popup window (options vary with application type), and then click OK. The name, type, and application unit of the selected monitor index automatically populate the Index, Threshold Type, and Application Unit fields.

¡ Threshold Condition—Select a threshold condition from the list (options vary with the monitor index type). For the Value type, options are Greater than or equal to and Less than or equal to. For the String type, options are Include and Exclude.

¡ Unit—Select a unit type of the monitor index from the list. The value depends on the monitor index type. Some indexes do not contain a unit type, such as the physical thread count of a .NET server.

6. Configure the Level-1 threshold parameters for the monitor index.

APM generates a major alarm when the monitor index meets the Level-1 threshold. If you enable the Level-2 threshold, APM generates a major alarm when the monitor index meets the Level-1 threshold but does not meet the Level-2 threshold.

¡ Enable Level-1 Threshold—Configure the Level-1 threshold setting for the monitor index.

¡ Threshold—If you enable the Level-1 threshold, set a Level-1 threshold value in the Threshold field.

¡ Trigger Times—If you enable the Level-1 threshold, set an alarm trigger frequency in the Trigger Times field. When the monitor index meets the Level-1 threshold once, the field value increases by one. APM generates a Level-1 threshold alarm if the monitor index meets the Level-1 threshold for the number of times specified by Trigger Times.

7. Configure the Level-2 threshold parameters for the monitor index.

APM generates a critical alarm when the monitor index meets the Level-2 threshold.

¡ Enable Level-2 Threshold—Configure the Level-2 threshold setting for the monitor index. If you enable the Level-2 threshold, set a Level-2 threshold value in the Threshold field. APM activates a critical alarm when the monitor index meets the threshold.

¡ Threshold—If you enable the Level-2 threshold, set a Level-2 threshold value in the Threshold field.

¡ Trigger Times—If you enable the Level-2 threshold, set an alarm trigger frequency in the Trigger Times field. When the monitor index meets the Level-2 threshold once, the field value increases by one. APM generates a Level-2 threshold alarm if the monitor index meets the Level-2 threshold for the number of times specified by Trigger Times.

8. Click OK.

Modifying global threshold configuration

To modify global threshold configuration of a monitor index:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Threshold Configuration.

The Global Threshold List is displayed.

4. Click the Modify icon for the threshold you want to modify.

The Modify Threshold page opens.

5. Modify basic parameters of the monitor index as needed:

¡ Application Type—Cannot be modified.

¡ Application Unit—Cannot be modified.

¡ Index—Cannot be modified.

¡ Threshold Type—Cannot be modified.

¡ Threshold Condition—Modify the threshold condition. Options vary with the monitor index type. For the Value type, options are Greater than or equal to and Less than or equal to. For the String type, options are Include and Exclude.

¡ Unit—Modify the threshold unit type. The value depends on the monitor index type. Some indexes do not contain a unit type, such as the physical thread count of a .NET server.

You cannot modify the application type, application unit, index, and threshold type.

6. Modify the Level-1 threshold parameters for the monitor index.

¡ Enable Level-1 Threshold—Modify the Level-1 threshold setting for the monitor index. You can modify the Level-1 threshold value or disable the Level-1 threshold as needed.

¡ Threshold—If you enable the Level-1 threshold, set a Level-1 threshold value in the Threshold field.

7. Modify the Level-2 threshold parameters for the monitor index.

APM generates a critical alarm when the monitor index meets the Level-2 threshold.

¡ Enable Level-2 Threshold—Modify the Level-2 threshold setting for the monitor index. You can modify the Level-2 threshold value or disable the Level-2 threshold as needed.

¡ Threshold—If you enable the Level-2 threshold, set a Level-2 threshold value in the Threshold field.

8. Click OK.

Deleting monitor indexes from threshold configuration

You can delete only the monitor indexes for which the threshold alarm function is manually enabled. After a monitor index is deleted, operators cannot set thresholds for the monitor index on the Threshold Setting page navigated from an application monitor report page or a custom application monitor report page.

To delete a monitor index:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Threshold Configuration.

The Global Threshold List opens.

4. Click the Delete icon for the monitor index you want to delete.

5. Click OK.

Configuring a monitor index to use global threshold or custom threshold

You can configure a monitor index to use a global threshold or custom threshold in the application monitor report or custom view report. By default, monitor indexes enabled with the threshold alarm function use global threshold.

To configure a monitor index to use global threshold or custom threshold:

1. Click the Resource tab.

2. Use one of the following methods to open the Threshold Setting page:

Method 1

a. From the navigation tree, click Application Manager > Application Monitor.

b. Click the target application name on the application monitor list.

c. Click the Set Threshold icon for the target monitor index on the application monitor report page.

For a monitor index not enabled with the threshold alarm function, enable the threshold alarm function for the monitor index. For more information, see "Adding threshold configuration."

Method 2

a. From the navigation tree, click Application Management > Custom View to open the custom monitor list.

b. Click the Monitor Report icon for the target custom monitor on the custom monitor list.

c. Click the Set Threshold icon for the target monitor index on the custom monitor report page.

For a monitor index not enabled with the threshold alarm function, enable the threshold alarm function for the monitor index. For more information, see "Adding threshold configuration."

NOTE:

The threshold you set for a monitor index on the application monitor report page also applies to the same monitor index on the custom monitor page. The threshold you set for a monitor index on the custom monitor page also applies to the same monitor index on the application monitor report page.

3. Select Custom or Global for Threshold Type.

¡ If you select Custom for the Threshold Type field, set a custom threshold for the monitor index. For more information, see "Modifying global threshold configuration."

¡ If you select Global for the Threshold Type field, the monitor index uses the global threshold set in the threshold configuration.

4. Click OK.

Exporting custom thresholds

1. Click the Resource tab.

2. From the navigation tree, select Application Management > Configurations.

3. Click Threshold Config.

4. Click Custom Thresholds.

5. Perform one of the following tasks:

¡ To export specific custom thresholds, select the thresholds, and then click Export.

¡ To export all custom thresholds, click Export All.

A dialog box opens.

6. Specify a path to save the exported file.

Modifying custom threshold configuration

To modify custom threshold configuration of a monitor index:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Threshold Configuration.

4. Click the Custom Threshold tab.

5. Click the Modify icon for the threshold you want to modify.

The Modify Threshold page opens.

6. Modify basic parameters of the monitor index as needed:

¡ Threshold Type—Select the Custom type.

¡ Unit—Modify the threshold unit type. The value depends on the monitor index type. Some indexes do not have a unit, such as the physical thread count of a .NET server.

7. Modify the Level-1 threshold parameters for the monitor index.

¡ Enable Level-1 Threshold—Modify the Level-1 threshold setting for the monitor index. You can modify the Level-1 threshold value or disable the Level-1 threshold as needed.

¡ Threshold—If you enable the Level-1 threshold, set a Level-1 threshold value in the Threshold field.

¡ Trigger Times—If you enable the Level-1 threshold, set an alarm trigger frequency in the Trigger Times field. APM generates a Level-1 threshold alarm if the monitor index meets the Level-1 threshold for the number of times specified by Trigger Times.

8. Modify the Level-2 threshold parameters for the monitor index.

APM generates a critical alarm when the monitor index meets the Level-2 threshold.

¡ Enable Level-2 Threshold—Modify the Level-2 threshold setting for the monitor index. You can modify the Level-2 threshold value or disable the Level-2 threshold as needed.

¡ Threshold—If you enable the Level-2 threshold, set a Level-2 threshold value in the Threshold field.

¡ Trigger Times—If you enable the Level-2 threshold, set an alarm trigger frequency in the Trigger Times field. APM generates a Level-2 threshold alarm if the monitor index meets the Level-2 threshold for the number of times specified by Trigger Times.

9. Click OK.

Baseline configuration

The baseline function of an application index can only be enabled or disabled globally. When you enable the baseline function for an application index, specify a baseline alarm level for the index.

Viewing the baseline configuration list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Baseline Configuration.

The baseline configuration list displays all application monitor indexes that can be enabled with the baseline function.

4. Click an application category to view monitor indexes for this application category.

The Application Type field also refreshes.

To view baseline configurations for all application categories, click Unlimited next to Application Category.

5. Click an application type to view the monitor indexes for this application type.

To view baseline configurations for all application types of an application category, click the application category, and then click Unlimited next to Application Type.

Baseline configuration list contents

¡ Application Type—Type of the application.

¡ Application Unit—Name of the application unit to which the baseline configuration belongs. Each application unit corresponds to an independent area in the application monitor report.

¡ Index—Name of the application monitor index that is enabled with the baseline function.

¡ Enabled—Displays whether the baseline function for the monitor index has been enabled.

¡ Shield Times—Interval for generating baseline alarms of the monitor index.

¡ Alarm Level—Level of the baseline alarm. Options are Critical, Major, and Minor.

¡ Modify—Click the Modify icon to modify the baseline configuration of the monitor index.

6. Click Refresh to refresh the baseline configuration list.

7. Click Back to return to the Configurations page.

Modifying baseline configuration

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Baseline Configuration.

4. Click the Modify icon for the baseline configuration you want to modify.

The Modify Baseline page opens.

5. Modify the following baseline configuration parameters:

¡ Application Type—Cannot be modified.

¡ Application Unit—Cannot be modified.

¡ Index—Cannot be modified.

¡ Enabled—Select whether to enable the baseline function for the index.

¡ Shield Times—Set an interval for generating baseline alarms of the index.

¡ Alarm Level—Select a baseline alarm level.

6. Click OK.

Port configuration

An application can listen to data and provide services through multiple ports. With these ports, APM finds applications running on the host and reads monitor indexes to calculate traffic statistics.

Port configuration allows operators to modify the settings of default application monitor port and traffic collection port for applications.

· Application Monitor Port—The Auto Discovery function scans the applications installed or deployed on a host through this type of ports.

· Traffic Collection Port—Applications use this type of port to provide services. Through these ports, APM can identify traffic of different application types running on the same IP address.

The following table displays the default port settings preloaded in APM. If an application does not have a default application monitor port, APM cannot detect the application through Auto Discovery. If an application does not have a default traffic collection port and the application is not an operating system, APM does not monitor its traffic. Operating system applications do not have default traffic collection ports, including Windows, AIX, SCO UNIX, FreeBSD, OpenBSD, HP-UX, Solaris, Mac OS, and Linux. APM identifies their traffic by IP address.

Table 12 Application default port list

Application type	Application monitor port	Traffic collection port
Windows Performance Counter	TCP 135	N/A
AIX FreeBSD HP-UX Linux Mac OS OpenBSD Solaris	TCP 23 (through Telnet) TCP 22 (through SSH)	N/A
SQL Server	TCP 1433	TCP 1433
MySQL	TCP 3306	TCP 3306
Oracle	TCP 1521	TCP 1521
DB2	TCP 50000	TCP 50000
DBQuery	N/A	N/A
Sybase	TCP 5000	TCP 5000
.NET Server	TCP 135	TCP 135
JBoss Server Tomcat Server	TCP 1099	TCP 1099
Oracle Application Server	TCP 8888	TCP 8888
WebLogic Server	TCP 7001	TCP 7001
Glassfish Server	TCP 8686	TCP 8686
WebSphere Server	TCP 8080	TCP 8080
Apache IIS Server PHP	TCP 80	TCP 80
Exchange 2003 Exchange 2007	TCP 135	TCP 135
POP3	TCP 110	TCP 110
SMTP	TCP 25	TCP 25
Office SharePoint	TCP 135	N/A
WebSphere MQ	TCP 1414	TCP 1414
REST Service SOAP Service	N/A	N/A
URL	TCP 80	N/A
Active Directory	TCP 135	TCP 135
LDAP Service	TCP 389	N/A
File Directory	N/A	N/A
SNMP Service	UDP 161	UDP 161
FTP Service	TCP 21	TCP 21
SFTP Service	TCP 22	TCP 22
DNS Service	TCP 53	TCP 53
Java Runtime	TCP 1099	TCP 1099

Viewing the application default port list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Port Configuration.

The Default Configuration list is displayed.

Default configuration list contents

¡ Application Type—Name of the application type.

¡ Application Monitor Port—Default port value that identifies the type of applications in Auto Discovery.

¡ Traffic Collection Port—Default port value for data traffic collection.

¡ Modify—Click the Modify icon to modify default port settings for the application type.

4. Click Refresh to refresh the application default port list.

5. Click Back to return to the Configurations page.

Modifying the application default port list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Port Configuration.

The Default Configuration list is displayed.

4. Click the Modify icon for the application type for which you want to modify the default ports.

5. Modify the following parameters:

¡ Application Type—Cannot be modified.

¡ Application Monitor Port—Modify the default port value that identifies the application type in Auto Discovery.

¡ Traffic Collection Port—Modify the default port value for traffic collection. For information about the application types for which you can modify the default traffic collection ports, see Table 12.

6. Click OK.

The modification has no effect on the applications already monitored.

Probe configuration

To collect traffic of applications, you must configure probes for APM to use. When no probes are configured or all probes are deleted, APM stops collecting application traffic and all application monitor reports no longer contain the application traffic area.

For operating system applications, probes identify their traffic by IP address. For other applications, probes identify their traffic by the combination of IP address and traffic collection port.

Probes must be installed and run on Linux. For more information about installing and configuring probes, see Probe Installation Guide.

Viewing the probe list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Probe Configuration.

The Probe List is displayed.

Probe list contents

¡ Name—Name of the probe. Click the name to view its details.

¡ IP Address—IP address of the probe.

¡ Description—Description of the probe.

¡ Modify—Click the Modify icon to modify the probe settings.

¡ Delete—Click the Delete icon to delete the probe.

4. Click Refresh to refresh the probe list.

Viewing the probe details

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Probe Configuration.

The Probe List is displayed.

4. Click the name of the probe whose details you want to view.

Probe details

¡ Name—Name of the probe.

¡ IP Address—IP address of the probe.

¡ Description—Description of the probe.

5. Click Back to return to the probe list.

Adding a probe

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Probe Configuration.

The Probe List is displayed.

4. Click Add.

5. Configure the following parameters:

¡ Name—Enter the name of the probe. The name must be unique in APM.

¡ IP Address—Enter the IP address of the probe.

¡ Description—Enter a description of the probe.

¡ Password—Enter the password of the probe. The value must be the same as that configured on the probe.

6. Click OK.

Modifying a probe

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Probe Configuration.

The Probe List is displayed.

4. Click the Modify icon for the probe you want to modify.

5. Configure the following parameters:

¡ Name—Modify the name of the probe. The name must be unique in APM.

¡ IP Address—Cannot be modified.

¡ Description—Modify the description of the probe.

6. Click OK.

Deleting a probe

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Probe Configuration.

The Probe List is displayed.

4. Click the Delete icon for the probe you want to delete.

A confirmation dialog box opens.

5. Click OK.

Deploying network configuration to probes

When you add an application monitor, APM automatically sends the network configuration (IP address or IP-to-port combination) of the monitored application to probes. If the network configuration failed to be delivered, troubleshoot the communication failure and manually deploy the network configuration to probes.

To deploy the network configuration of monitored applications to probes:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Probe Configuration.

The Probe List is displayed.

4. Click Deploy.

APM deploys the network configuration of monitored applications to all probes on the list.

Parameter configuration

APM operating parameters include the monitor data retention periods and data background colors.

To modify APM operating parameters:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Parameter Configuration.

4. Configure the following parameters as needed:

¡ Original Data Retention Time (Day)—Enter how many days APM will keep the original data collected from applications.

¡ Hourly Data Retention Time (Month)—Enter how many months APM will keep the hourly application data that is aggregated from the original data.

¡ Daily Data Retention Time (Year)—Enter how many years APM will keep the daily application data that is aggregated from the original data.

¡ Threshold-1 Color—Enter the RGB value of the background color for the monitor index data that meets the threshold-1 condition. Or you can click the box to select a color from the popup color panel. The default setting is RGB FFD200, representing orange.

¡ Threshold-2 Color—Enter the RGB value of the background color for the monitor index data that meets the threshold-2 condition. Or you can click the box to select a color from the popup color panel. The default setting is RGB FF0000, representing red.

¡ Whether IDC Environment—Select Yes or No from the list. If you select Yes, you switch to the IDC cloud tenant environment, where the system displays functions according to your privileges, and you cannot switch back to non-IDC environment.

5. Click OK next to each parameter you have configured.

6. Click Back to return to the Configurations page.

APM administrator configuration

This feature is available only in IDC environment. Use this feature to configure the APM administrator privileges for an operator in the IMC system. For information about adding an operator to IMC, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

Viewing the APM administrator list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click APM Administrator Configuration.

The APM Administrator Configuration page opens.

APM Administrator configuration list contents

¡ Operator Name—Name used by the operator to log in to IMC.

¡ Operator Full Name—Full name of the operator.

¡ Type—Operator type. Options are System and Tenant. The System administrator has super administrator privileges.

¡ APM Server—APM server that can be managed by the operator.

¡ Modify—Click the Modify icon to modify the operator configuration.

¡ Delete—Click the Delete icon to delete the operator.

4. Click Refresh to refresh the APM administrator list.

Adding an APM administrator

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click APM Administrator Configuration.

The APM Administrator Configuration page opens.

4. Click Add.

The Add page opens.

5. Configure the following basic information:

¡ Operator—Select an operator from the list.

¡ Type—Select the operator type. Options are System and Tenant.

¡ APM Server—Select the APM server that can be managed by the operator. The server 127.0.0.1 represents a centralized APM server or the primary server of a distributed APM server system. A System administrator can manage all servers by default.

6. Click OK.

Modifying an APM administrator

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click APM Administrator Configuration.

The APM Administrator Configuration page opens.

4. Click the Modify icon for the APM administrator you want to modify.

5. The Modify page opens.

6. Configure the following basic information:

¡ Operator—Select an operator from the list.

¡ Type—Select the operator type. Options are System and Tenant.

7. Click OK.

Deleting a template

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click APM Administrator Configuration.

The APM Administrator Configuration page opens.

4. Click the Delete icon for the APM administrator you want to delete.

A confirmation dialog box opens.

5. Click OK.

Template configuration

APM provides application and agent templates. When you add application monitors or install agents remotely, use correct templates for them to simplify the configuration.

Viewing the template configuration list

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Template Configuration.

The Template Configuration page opens.

Template configuration list contents

¡ Template Name—Name of the template.

¡ Type—Type of the template. Options are Application Template (Application type), Agent Template(Windows), and Template(Linux).

¡ Description—Description of the template.

¡ Modify—Click the Modify icon to modify the template configuration.

¡ Delete—Click the Delete icon to delete the template.

4. Click Refresh to refresh the template configuration list.

Adding an agent template

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Template Configuration.

The Template Configuration page opens.

4. Click Add Template.

The Select Template Type window opens.

5. Select Agent Template.

6. Click OK.

The Add Agent Template page opens.

7. Configure the following basic host information:

¡ Template Name—Enter a name for the template.

¡ Host Type—Select the host type that is compatible with the template. Options are Windows and Linux.

¡ Installation Path—Enter the absolute path used in the agent installation on the target host.

¡ Username—Enter the name of the user that has the administrator's privileges on the target host.

¡ Password—Enter the password for the user that has the administrator's privileges on the target host.

¡ Description—Enter a description for the template.

8. Click OK.

Adding an application template

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Template Configuration.

The Template Configuration page opens.

4. Click Add Template.

The Select Template Type window opens.

5. Select Application Template.

6. Select an application type from the Application Type list.

7. Click OK.

The page for adding an application template for the selected application type opens.

8. Configure the application monitoring parameters.

Different application types require different monitoring parameters. For more information, see the sections about adding application monitors for different application types.

9. Click OK.

Modifying an agent template

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Template Configuration.

The Template Configuration page opens.

4. Click the Modify icon for the agent template you want to modify.

The Modify Agent Template page opens.

5. Modify the following basic host information:

¡ Template Name—Cannot be modified.

¡ Host Type—Enter the host type that is compatible with the template. Options are Windows and Linux.

¡ Installation Path—Enter the absolute path used in the agent installation on the target host.

¡ Username—Enter the name of the user that has the administrator's privileges on the target host.

¡ Password—Enter the password for the user that has the administrator's privileges on the target host.

¡ Description—Enter a description of the template.

6. Click OK.

Modifying an application template

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Template Configuration.

The Template Configuration page opens.

4. Click the Modify icon for the application template you want to modify.

The Modify Application Template page opens.

5. Modify application monitoring parameters.

Different application types require different monitoring parameters. For more information, see the sections about adding application monitors for different application types.

6. Click OK.

Deleting a template

Deleting templates does not affect existing applications and agents.

To delete a template:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Configurations.

The Configurations page opens.

3. Click Template Configuration.

The Template Configuration page opens.

4. Click the Delete icon for the template you want to delete.

A confirmation dialog box opens.

5. Click OK.

Application data display

APM displays application data by using widgets and a dashboard. You can custom the IMC home page or configure the dashboard to display data. For more information about the IMC home page and the dashboard, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

Widgets

You can custom widgets on the IMC home page. APM supports the Application Topology widget, Application Monitor widget, and Host Monitor widget.

Application Topology widget

Figure 40 shows the Application Topology widget. In the widget, you can view the availability and health states of applications, how applications and hosts are related to each other, and how the hosts are connected to the access devices and the physical network. The widget supports the same functions and operations as the application topology does. For more information, see "Topology and application group management."

Figure 40 Application Topology widget

By default, APM refreshes the Application Topology widget every 10 minutes.

To set the refresh interval for the Application Topology widget:

1. Log in to IMC and add the Application Topology widget to the home page.

2. Click the Set icon in the right top corner of the Application Topology widget.

3. Click Refresh Interval to open the Setting page.

4. Select an interval from the list. Options are No Refresh, 1, 5, 10 and 30, in minutes. If you select No Refresh, click the Refresh icon in the right top corner of the widget to view the latest topology.

5. Click OK.

Application Monitor widget

Figure 41 shows an Application Monitor widget. The contents displayed in the widget are the same as those in the application monitor list. Operators can control the displayed contents by customizing the application monitor list. For more information about customizing the application monitor list, see "Monitor management."

Figure 41 Application Monitor widget

Some contents of an application monitor widget might not be displayed due to the home page layout of IMC and browser window size. You can click the Move Left or Move Right icon on the title bar of the widget to view the contents that are not displayed.

By default, APM refreshes the Application Monitor widget every 10 minutes. You can modify the refresh interval and specify which applications to display.

Setting the filter conditions

The IMC home page can contain multiple Application Monitor widgets, each of which focuses on a group of applications filtered by application type, availability, or health state.

To set the filter conditions:

1. Log in to IMC and add an Application Monitor widget to the home page.

2. Click the Set icon in the right top corner of the Application Monitor widget.

3. Click Settings to open the Setting page.

4. Specify the following parameters to filter applications to display in the widget:

¡ Name—Enter the name of the application monitor.

¡ Application Type—Select an application type from the list. For information about the options, see "Application Manager overview."

¡ Availability—Select availability from the list. Options are Unlimited, Available, Inaccessible, Unavailable, and Unmanaged.

¡ Health State—Select a health state from the list. Options are Unlimited, Healthy, Minor, Major, Critical, and --. The two consecutive hyphens (--) indicates that the application is inaccessible or unmanaged.

5. Click Query. The widget displays the target applications.

6. Click Reset. The widget displays all applications.

Setting the refresh interval

To set the refresh interval for an application monitor widget:

1. Log in to IMC and add an Application Monitor widget to the home page.

2. Click the Set icon in the right top corner of the Application Monitor widget.

3. Click Refresh Interval to open the Setting page.

4. Select an interval from the list. Options are No Refresh, 1, 5, 10, and 30, in minutes. If you select No Refresh, click the Refresh icon in the right top corner of the widget to view the latest data.

5. Click OK.

Host Monitor widget

Figure 42 illustrates the Host Monitor widget. In the widget, you can monitor the OS, CPU usage, content usage, availability, and health state of each host directly. You can open the operating system monitor report by clicking its name.

Figure 42 Host Monitor widget

Setting the refresh interval

By default, APM refreshes the Host Monitor widget every 10 minutes.

To set the refresh interval for the widget:

1. Log in to IMC and add the Host Monitor widget to the home page.

2. Click the Set icon in the right top corner of the Host Monitor widget.

3. Click Refresh Interval to open the Setting page.

4. Select an interval from the list. Options are No Refresh, 1, 5, 10, and 30, in minutes. If you select No Refresh, the widget does not automatically refresh. To view the latest data, you must click the Refresh icon in the right top corner of the widget.

5. Click OK.

Dashboard

APM can display application data in the dashboard. The following information describes the widgets supported by the dashboard.

Application List widget

The Application List widget displays application monitor parameters, as shown in Figure 43. For more information about the application monitor list, see "Monitor management."

Figure 43 Application List widget

To configure the Application List widget:

1. Point to the My Favorites icon .

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the Application List widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Click the Save icon .

An informational dialog box opens.

5. Click OK.

Server-Memory widget

The Server-Memory widget displays the memory usage trend of servers in the most recent 1 hour, as shown in Figure 44.

Figure 44 Server-Memory widget

To configure the Server-Memory widget:

1. Point to the My Favorites icon .

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the Server-Memory widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Right-click the Server Memory Usage area and select Configure Parameters.

5. Select servers, and then click OK.

6. Click the Save icon .

An informational dialog box opens.

7. Click OK.

Application Group widget

The Application Group widget has the same functions and operations as the group topology. For information about the functions and operations of the widget, see "Topology and application group management."

Figure 45 Application Group widget

To configure the Application Group widget:

1. Point to the My Favorites icon.

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the Application Group widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Right-click the Application Group area and select Configure Parameters.

5. Select an application, and then click OK.

6. Click the Save icon .

An informational dialog box opens.

7. Click OK.

Server-CPU widget

The Server-CPU widget displays the CPU usage trend of servers in the most recent 1 hour, as shown in Figure 46.

Figure 46 Server-CPU widget

To configure the Server-CPU widget:

1. Point to the My Favorites icon.

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the Server-CPU widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Right-click the Server CPU Usage area and select Configure Parameters.

5. Select servers, and then click OK.

6. Click the Save icon .

An informational dialog box opens.

7. Click OK.

Server-Flux widget

The Server-Flux widget displays the receive traffic (Rx) and send traffic (Tx) of servers in the most recent 1 hour, as shown in Figure 47.

Figure 47 Server-Flux widget

To configure the Server-Flux widget:

1. Point to the My Favorites icon.

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the Server-Flux widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Right-click the Server Traffic area and select Configure Parameters.

5. Select servers, and then click OK.

6. Click the Save icon .

An informational dialog box opens.

7. Click OK.

Server-Disk widget

The Server-Disk widget displays the disk usage of servers, as shown in Figure 48.

Figure 48 Server-Disk widget

To configure the Server-Disk widget:

1. Point to the My Favorites icon.

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the Server-Disk widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Right-click the Server Disk Usage area and select Configure Parameters.

5. Select servers, and then click OK.

6. Click the Save icon .

An informational dialog box opens.

7. Click OK.

URL Sequence widget

The URL Sequence widget displays the status of a URL sequence, whose content is the same as the URL sequence monitor report. For more information, see "HTTP service monitor."

Figure 49 URL Sequence widget

To configure the URL Sequence widget:

1. Point to the My Favorites icon.

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the URL Sequence widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Right-click the URL Sequence area and select Configure Parameters.

5. Select a URL sequence application, and then click OK.

6. Click the Save icon .

An informational dialog box opens.

7. Click OK.

Application Topology widget

The application topology widget has the same functions and operations as the application topology. For more information, see "Topology and application group management."

Figure 50 Application Topology widget

To configure the Application Topology widget:

1. Point to the My Favorites icon.

2. From the menu that opens, select Dashboard > Configuration.

The dashboard configuration window opens.

3. In the widget area, select the Application Topology widget icon and drag it to the panel below.

To change the widget size, drag the widget frames.

4. Click the Save icon .

An informational dialog box opens.

5. Click OK.

Windows OS monitor

APM monitors the following Windows OS applications:

· Windows

· Windows performance counters

This chapter describes how to add and modify Windows OS application monitors, and helps you view relevant monitor reports.

Windows

Windows operating systems provide a base platform for a variety of desktop-oriented applications. To ensure service quality, its performance and stability must be guaranteed.

Adding a Windows application monitor

APM can locally or remotely monitor Windows operating systems through WMI or SNMP. When you add Windows application monitors, follow these guidelines:

· To monitor a Windows operating system through an agent, deploy the agent on the host on which the Windows operating system is installed. For more information about agents, see "APM agent management."

· To monitor a Windows operating system through WMI:

¡ Enable and configure WMI for the host on which the Windows operating system is installed. For more information about enabling WMI on Windows, see the Microsoft Windows online help.

¡ Obtain the username and password of the user who has the Windows administrator's privileges.

· To monitor a Windows operating system through SNMP:

¡ Enable and configure SNMP for the host on which the Windows operating system is installed. For more information about enabling SNMP on Windows, see the Microsoft Windows online help.

¡ Obtain the read-only and read-write community strings.

· Add the Windows hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the Window operating system application, make sure at least one probe is configured in APM. After a Windows application monitor is added, APM sends the IP address of the monitored Windows operating system application to the probes for traffic collection.

The following task is performed in remote monitor mode. When the local monitor mode is used, you need to configure only part of the parameters that are required for the remote monitor mode.

To add a Windows application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Management > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click Windows of the Windows Server Monitor class.

The page for adding a Windows application monitor opens.

4. Configure the following parameters for the application monitor:

¡ IP Address—Enter the IP address of the host where the Window operating system to be monitored is installed. APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host from the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Template—Click the Configure icon next to the Template field to select an existing template. The Template field is automatically populated with the name of the selected template. For more information about configuring application templates, see "Configuration management." This field is displayed only when you select Enable from the Use Template list.

¡ Description—Enter a description for the application monitor.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval improves real-time data accuracy at the expense of system resources. This field is available only when you select Disable from the Use Template list.

¡ Monitor Type—Select the protocol (SNMP or WMI) through which APM monitors the application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SNMP is selected, configure the following parameters:

- Edit SNMP Parameters—Select this option if you want to manually configure SNMP parameters for APM. Make sure the SNMP settings are the same as those on the Windows host.

- Select an Existing Template—Select this option if you want to select an existing SNMP template for APM. For information about setting SNMP parameter templates, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

- Parameter Type—Select the SNMP parameter type. Options are SNMPv1, SNMPv2c, and SNMPv3 Template. The SNMPv3 Template option is available only when Select an Existing Template is selected.

- Read-Only Community String—Enter the SNMP read-only community string, with which APM can read MIB variables from the Windows host.

- Read-Write Community String—Enter the read-write SNMP community string, with which APM can read MIB variables from or write MIB variables to the Windows host.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for an SNMP response from the Windows host. The value range is 1 to 60 seconds and the default is 4 seconds. If no SNMP response is received from the Windows host within the timeout time, APM considers the interaction a failure.

- Retries (1-20)—Enter how many times APM retries to send SNMP packets to the Windows host.

When WMI is selected, configure the following parameters:

- Username—Enter the username of the Windows administrator.

If the administrator is a domain user, use domain name\username.

If the administrator is a local user, use host name\username, IP address\username, or username.

- Password—Enter the password of the administrator.

- Enable Event Logging—Select Enable or Disable from the list. If you select Enable, configure the event logging threshold and type. The event logging type can be Error, Warning, Information, Security Audit Success, or Security Audit Failure.

¡ Contact—Enter contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor. This field is available only when you select Disable from the Use Template list.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of Windows applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that Windows depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the Windows application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not specified, APM adds the application monitor without verifying the connection.

5. Click OK.

Modifying a Windows application monitor

Authorized users can modify all parameters except the IP address and the APM server for a Windows application monitor. When the IP address of a Windows host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a Windows application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Modify icon for the Windows application monitor you want to modify.

The page for modifying the Windows application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a Windows application monitor."

5. Click OK.

Viewing the Windows application monitor report

After adding a Windows operating system application monitor, APM collects application index data to calculate its availability and health status. You can obtain monitor indexes for the Windows operating system by viewing the monitor report.

To view the Windows application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a Windows application monitor to display the report.

Figure 51 shows part of a Windows application monitor report.

Figure 51 Part of a Windows application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the Windows operating system.

· IP Address—Windows host IP address.

· Application Type—Type of the monitored application, which is always Windows.

· Version—Version of the Windows operating system.

· System Running Time—Duration since the startup of the Windows application to the time when APM last polled the Windows application.

· Last Polling Time—Time when APM last polled the Windows operating system.

· Relationship—Click the Relationship icon to view dependencies between the Windows application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the Windows operating system. This field is not displayed if no alarm is generated by the Windows operating system.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the Windows operating system in the last polling interval.

¡ Click the Weekly History icon to view the availability of the Windows operating system in the last 7 days.

¡ Click the Monthly History icon to view the availability of the Windows operating system in the last 30 days.

· Available Time—Total amount of time that the Windows operating system was available after 00:00 today.

· Unavailable Time—Total amount of time that the Windows operating system was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the Windows operating system was unavailable after 00:00 today.

· Unmanaged Time—Total amount of time that the Windows operating system was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage of the Windows operating system in the last polling interval.

¡ Click the Set Threshold icon to set the CPU usage alarm thresholds for the Windows operating system.

¡ Click the History Record icon to view statistics of the history graph of the CPU usage for the Windows operating system.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the Windows application, which corresponds to the physical memory bar.

· Swap—Swap memory of the Windows application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

CPU Performance

The CPU Performance area contains the following fields:

· CPU Name—Name of the Windows server CPU.

· Privileged Time—Percentage of the privileged time to the total running time of the system.

· Processor Time—CPU usage ratio of the system.

· User Time—Percentage of the CPU user time to the total running time of the system.

· Interrupt Time—Percentage of the CPU interrupts time to the total running time of the system.

· Interrupts Rate—Number of CPU interrupts per second.

You can click the History Record icon to view the history graph of a monitor index.

Paging

The Paging area contains the following fields:

· Cache—Total cache capacity for paging.

· Page Faults Rate—Number of page faults per second.

· Page Reads Rate—Number of page reads per second.

· Page Writes Rate—Number of page writes per second.

· Pages Input Rate—Number of page inputs per second.

· Pages Output Rate—Number of page outputs per second.

You can click the History Record icon to view the history graph of a monitor index.

Ping Test

APM pings the Windows host every polling interval. In a ping test, APM sends up to three ICMP packets to the host. When APM receives a response, it considers the ping test a success and records the response time. When APM receives no response after three tries, it considers the ping test a failure.

The Ping Test area contains the following fields:

· Response Time—Ping response time in the last ping test. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets sent in the last ping test. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

· Packets Received—Number of ICMP responses received by APM in the last ping test. The value is 0 or 1. Click the History Record icon to view the history graph of the received packets.

Service

By default, APM does not monitor any service, and the service list is empty. APM collects state information of services after they are selected.

The Service area contains the following fields:

· Config—Click the Config icon to populate the Application Instance List with all detected services running on the Windows operating system. Select the desired services, and then click OK. APM collects state information about the selected services in the next polling interval.

· Service Name—Original name of the service.

· Display Name—Service name or alias displayed on the Windows service console. For example, on the Windows service console, the DHCP client service uses the alias DHCP Client Service rather than the original name Dhcp. Typically, the display name identifies a service more clearly.

· State—State of the service in the last polling interval. Click the Start Service icon or Stop Service icon to start or stop a service. This function is available only for Windows operating systems monitored through WMI on IMC installed on a Windows server

Disk Usage Ratio

Use the Disk Usage Ratio area layout to view how data is allocated on each root disk (physical disk, partition, or logical volume).

The Disk Usage Ratio area contains the following fields:

· Disk—Drive letter of the disk, which can be a physical drive, a partition, or a logical volume.

· Usage Ratio—Disk space usage.

¡ Click the Set Threshold icon for a disk to set space usage alarm thresholds for it.

¡ Click the History Record icon for a disk to view statistics of the history graph of the space usage of the disk.

· In Use—Used space of the disk. Click the History Record icon to view the history graph of the used disk space.

· Free Space—Free space of the disk. Click the History Record icon to view the history graph of the free disk space.

Share Disk

The Share Disk area contains the following fields:

· Share Disk Name—Name of a share disk on the Windows server.

· Share Disk Usage Ratio—Usage ratio of the share disk.

· Share Disk In Use—Used space of the share disk.

· Share Disk Size—Total space of the share disk.

· Share Disk Incremental—Incremental between two successive collections.

· Share Disk Path—Share path of the share disk.

You can click the History Record icon to view the history graph of a monitor index.

I/O State

The I/O State area contains the following fields:

· Disk Name—Name of a disk on the Windows server.

· I/O Read&Write Rate—Rate at which bytes are transferred to or from the disk during write or read operations.

· I/O Read Rate—Rate at which bytes are transferred from the disk during read operations.

· I/O Write Rate—Rate at which bytes are transferred to the disk during write operations.

· Disk Queue Length—Number of requests outstanding on the disk at the time the performance data is collected.

· Disk Read Time—Percentage of disk read time.

· Disk Write Time—Percentage of disk write time.

· Disk Reads Rate—Number of disk reads per second.

· Disk Writes Rate—Number of disk writes per second.

You can click the History Record icon to view the history graph of a monitor index.

Application Traffic

APM collects traffic statistics for the Windows operating system based on the IP address of the Windows host when probes are added to APM.

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by the Windows operating system over the last 1 hour.

· Today's Traffic—Total traffic sent and received by the Windows operating system since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Name of the network interface card (NIC). APM monitors both physical and virtual (logical) network interface cards.

· Bandwidth—Maximum bandwidth of the NIC.

· Receive Rate—Receive rate of the NIC in the last polling interval.

¡ Click the Set Threshold icon for the NIC to set alarm thresholds for the receive rate.

¡ Click the History Record icon to view the history graph of the receive rate.

· Send Rate—Send rate of the NIC in the last polling interval.

· Input Error Packet Rate—Number of inbound erroneous packets per second on the NIC in the last polling interval.

· Output Error Packet Rate—Number of outbound erroneous packets per second on the NIC in the last polling interval.

TCP Connections

The TCP Connections area contains the following fields:

· Active Connections Rate—Number of active connections per second.

· Passive Connections Rate—Number of passive connections per second.

· Failed Connections Rate—Number of failed connections per second.

· Reset Connections Rate—Number of reset connections per second.

· Established Connections—Number of established connections.

· Received Segments Rate—Number of received segments per second.

· Sent Segments Rate—Number of sent segments per second.

· Retransmitted Segments Rate—Number of retransmitted segments per second.

Click the History Record icon to view the history graph of a monitor index.

Adapter

The Adapter area contains the following fields:

· Adapter ID—Device ID of the adapter.

· Adapter Type—Type of the adapter.

· Max Speed—Maximum transmission speed of the adapter.

· Net Connection Status—Network connection status of the adapter. Values include:

¡ Disconnect

¡ Connecting

¡ Connected

¡ Disconnecting

¡ Hardware Not Present

¡ Hardware Disabled

¡ Hardware Malfunction

¡ Media Disconnected

¡ Authenticating

¡ Authentication Succeeded

¡ Authentication Failed

¡ Invalid address

¡ Credentials Required

· Last Reset Time—Last reset time of the adapter.

· MAC Address—MAC address of the adapter.

· Adapter Description—Description of the adapter.

Process

By default, APM does not monitor any process, and the process list is empty. APM collects CPU and memory usages of selected processes.

The Process area contains the following fields:

· Config—Click the Config icon to quickly populate the Application Instance List with all detected processes running on the Windows operating system. Select the desired processes, and then click OK. APM collects CPU and memory usages of the selected processes in the next polling interval.

· Process Name—Name of the process.

· CLI—Command line used to start the process.

· CPU Usage—CPU usage of the process in the last polling interval.

¡ Click the Set Threshold icon for a process to set CPU usage alarm thresholds for the process.

¡ Click the History Record icon for a process to view the CPU usage history graph for the process.

· Memory Usage—Memory usage of the process in the last polling interval. Click the History Record icon for a process to view the memory usage history graph for the process.

Process Number

The Process Number area contains the following field:

Process Number—Number of processes on the Windows server.

Thread Number

The Thread Number area contains the following field:

Thread Number—Number of threads on the Windows server.

Event

To monitor Windows events in APM, ensure the Monitor Type is set to WMI and the Enable Event Logging option is selected for the Windows application monitor.

The Event area contains the following fields:

· Generation Time—Time when the event occurred.

· Event Type—Type of the event. When adding Windows application monitors, you can specify event types. Options are Error, Warning, Information, Security Audit Success, and Security Audit Failure.

· Log File—File that records the event.

· Event Code—Event ID that is defined by Windows.

· Source Name—Source of the event.

· Event Category—Category of the event.

· Description—Description of the event.

Memory Info

The Memory Info area contains the following fields:

· Tag—Memory card tag on the Windows server.

· Capacity—Capacity of memory.

· Device Locator—Position of the memory card on the Windows server.

CPU Info

The CPU Info area contains the following fields:

· CPU DeviceID—Device ID of the CPU.

· Cores—Number of CPU cores.

· Logical Processors—Number of logical processors of the CPU.

· CPU Name—Name of the CPU.

· Manufacturer—Manufacturer of the CPU.

· Clock Speed—Clock speed of the CPU.

Base Board

The Base Board area contains the following fields:

· Serial Number—Serial number of the base board.

· Manufacturer—Manufacturer of the base board.

· Product—Model of the base board.

· Status—Status of the base board.

Fan Info

The Fan Info area contains the following fields:

· Fan Name—Name of the fan.

· Fan Status—Status of the fan.

Host

The Host area contains the following fields:

· Manufacturer—Manufacturer of the host.

· Model—Model of the host.

· Host Name—Name of the host.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product that the board applies to.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

Windows performance counters

Microsoft Windows performance counters monitor the performance data of various Microsoft products. Windows performance counters monitor belongs to the common monitor. APM can read the values of the performance counters to help you monitor Microsoft products.

Adding a Windows performance counter application monitor

APM can locally or remotely monitor Windows performance counters through WMI. When you add Windows performance counters application monitors, follow these guidelines:

· To monitor a Windows operating system through WMI:

¡ Enable and configure WMI for the host on which the Windows operating system is installed. For more information about enabling WMI on Windows, see the Microsoft Windows online help.

¡ Obtain the username and password of the user who has the Windows administrator's privileges.

· Add the Windows hosts to the IMC platform so APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· One application monitor can monitor at most 20 performance counters on an operating system. To monitor more performance counters, add more application monitors for the operating system.

The following task is performed in remote monitor mode. When the local monitor mode is used, you need to configure only part of the parameters that are required for the remote monitor mode.

To add a Windows performance counter application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Management > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click Performance Counter of the Windows Server Monitor class.

The page for adding a Windows performance counter application monitor opens.

4. Configure the following parameters for the application monitor:

¡ IP Address—Enter the IP address of the host where the Window operating system hosting the performance counters to be monitored is installed. If the host is already added to the IMC platform, you can also click Select, and then select the host from the Select Devices window. For information about selecting a host, see "Quick start." APM automatically checks the specified IP address and associates the application monitor with the host in the IMC platform.

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Username—Enter the username of the Windows administrator. This field is available only when you select Disable from the Use Template list.

- If the administrator is a domain user, use domain name\username.

- If the administrator is a local user, use host name\username, IP address\username, or username.

¡ Password—Enter the password of the administrator. This field is available only when you select Disable from the Use Template list.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of Windows performance applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that the Windows performance counter depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology. APM automatically adds the dependencies between the Windows performance counter and operating system applications by IP address and displays their dependencies in the application topology.

¡ Application Group—Specify an application group for the Windows performance counter application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

5. Click OK.

NOTE:

The performance counters to be monitored are configured in the monitor report of the Windows performance counter application. You do not need to specify them when adding the application monitor.

Modifying a Windows performance counter application monitor

Authorized users can modify all parameters except the IP address and the APM server for a Windows performance counter application monitor. When the IP address of a Windows performance counter host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a Windows performance counter application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Modify icon for the Windows performance counter application monitor you want to modify.

The page for modifying the Windows performance counter application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a Windows performance counter application monitor."

5. Click OK.

Viewing the Windows performance counter application monitor report

After adding a Windows performance counter application monitor, operators must specify in the monitor report which performance counters are to be monitored. APM collects the index data of the specified performance counters to calculate their availability and health status. You can obtain monitor indexes for the performance counters by viewing the monitor report.

To view the Windows performance counter application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a Windows performance counter application monitor to display the report.

Figure 52 shows part of a Windows application monitor report.

Figure 52 Part of a Windows performance counter application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the Windows performance counter.

· IP Address—IP address of the host running the Windows operating system.

· Application Type—Type of the monitored application, which is always Performance Counter.

· Last Polling Time—Time when APM last polled the Windows performance counter.

· Relationship—Click the Relationship icon to view dependencies between the Windows performance counter and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the Windows performance counter. This field is not displayed if no alarm is generated by the Windows performance counter.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the Windows performance counter in the last polling interval.

¡ Click the Weekly History icon to view the availability of Windows performance counter in the last 7 days.

¡ Click the Monthly History icon to view the availability of the Windows performance counter in the last 30 days.

· Available Time—Total amount of time that the Windows performance counter was available after 00:00 today.

· Unavailable Time—Total amount of time that the Windows performance counter was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the Windows performance counter was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the Windows performance counter was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

Ping Test

APM pings the host where the Windows performance counters are located at every polling interval. In a ping test, APM sends out a maximum of three ICMP packets to the host. When it receives a response, APM considers the ping test a success and records the response time. If it does not receive a response after sending three ICMP packets, APM considers the ping test a failure.

The Ping Test area contains the following fields:

· Response Time—Ping response time in the last ping test. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets sent in the last ping test. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

· Packets Received—Number of ICMP responses received by APM in the last ping test. The value is 0 or 1. Click the History Record icon to view the history graph of the received packets.

Performance Counter

By default, the performance counter list is empty. APM collects the index data of the selected performance counters. You can monitor up to 20 performance counters in one application monitor.

The Performance Counter area contains the following fields:

· Config—Click the Config icon to populate the Application Instance List with all detected performance counters on the Windows operating system. Select the desired performance counters, and then click OK. APM collects index data of the selected performance counters in the next polling interval.

· Category—Category of the performance counter. The performance counter category corresponds to the Level-1 menu item in the left navigation tree of the Application Instance List window.

· Instance—Instance of the performance counter category. For example, the Win32_PerfFormattedData_PerfOS_Processor category contains four instances, 1, 2, 3, 4, and _Total, which in turn represent CPU cores 1, 2, 3, 4, and the total CPU. The instance corresponds to the Level--2 menu item in the left navigation tree of the Application Instance List window.

· Attribute/Value—Performance counter name and data.

Detailed information about performance counter

This area displays detailed information of each monitored performance counter.

The Detailed information area contains the following fields:

· Catalog/Instance—Category and instance name of the performance counter.

· Attribute/Value—Attribute and value collected for the performance counter in the last polling interval.

UNIX server monitor

AIX

AIX can be installed on various types of IBM servers. The performance and stability of AIX greatly affects the performance of applications running on it.

Adding an AIX application monitor

APM monitors AIX applications through CLI. When you add AIX application monitors, follow these guidelines:

· Enable Telnet or SSH on AIX. For more information, see the AIX configuration guide.

· Obtain the username and password of the Telnet or SSH user who has the AIX administrator's privileges.

· Add AIX hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the AIX application, make sure at least one probe is configured in APM. After an AIX application monitor is added, APM sends the IP address of the monitored AIX application to the probes for traffic collection.

To add an AIX application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

¡ From the navigation tree, select Application Manager > Application Monitor. In the application monitor list, click Add.

The Add Application page displays all application types that can be monitored by APM.

3. Click AIX of the UNIX Server Monitor class.

The page for adding an AIX application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the AIX application to be monitored is installed. APM automatically checks the IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Monitor Type—Select the protocol (SSH or Telnet) through which APM monitors the AIX application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on AIX.

- Select an Existing Template—Select this option if you want to select an existing SSH template for APM. For information about setting SSH parameter templates, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

- Authentication Mode—Select the authentication mode for SSH users. Options are Password, Private Key, Password + Private Key, Password + Super Password, Private Key + Super Password, and Password + Private Key + Super Password. The following parameters to be configured vary with authentication modes.

- Username—Enter the SSH username. The user must have the AIX administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on AIX.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from AIX. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from AIX within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the AIX host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on AIX.

- Select an Existing Template—Select this option if you want to select an existing Telnet template for APM. For information about setting Telnet parameter templates, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

- Authentication Mode—Select the authentication mode for Telnet users. Options are Password (No Operator or Super/Manager), Username + Password, Super/Manager Password, Password + Super/Manager Password (No Operator), Username + Password + Super/Manager Password, No Username + No Password, and Username + No Password. The following parameters to be configured vary with authentication modes.

- Username—Enter the Telnet username. The user must have the AIX administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from AIX. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from AIX within the timeout time, APM considers that the interaction has failed.

¡ Contact—Enter user contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor. This field is available only when you select Disable from the Use Template list.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of AIX applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that AIX depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the AIX application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. APM verifies the application connectivity by using the previous parameter settings, and adds the application monitor only when it can connect to the application. If you do not select this parameter, APM adds the application monitor without verifying the application connectivity.

5. Click OK.

Modifying an AIX application monitor

Authorized users can modify all parameters except the IP address and the APM server for an AIX application monitor. When the IP address of a monitored AIX host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify an AIX application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click AIX of the UNIX Server Monitor class.

4. Click the Modify icon for the AIX application monitor you want to modify.

The page for modifying the AIX application monitor opens.

5. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding an AIX application monitor."

6. Click OK.

Viewing the AIX application monitor report

After an AIX application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for AIX by viewing the monitor report.

To access the AIX application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of an AIX application monitor to display the report.

Figure 53 shows part of an AIX monitor report.

Figure 53 Part of an AIX application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored AIX application.

· IP Address—IP address of the AIX host.

· Application Type—Type of the monitored application, which is always AIX.

· Version—Version of the AIX operating system.

· System Running Time—Duration since the startup of the AIX application to the time when APM last polled the AIX application.

· Last Polling Time—Time when APM last polled the AIX application.

· Relationship—Click the Relationship icon to view dependencies between the AIX application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the AIX host. If no alarm is generated by AIX, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the AIX application in the last polling period.

¡ Click the Weekly History icon to view the availability of the AIX application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the AIX application in the last 30 days.

· Available Time—Total amount of time that the AIX application was available after 00:00 today.

· Unavailable Time—Total amount of time that the AIX application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the AIX application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the AIX application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the AIX application in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the AIX application, which corresponds to the physical memory bar.

· Swap—Swap memory of the AIX application, which corresponds to the disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the memory (including the physical memory and swap memory) usage.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

CPU Performance

The CPU Performance area contains the following fields:

· CPU Name—Name of the AIX server CPU.

· Load Percentage—Percentage of the load time.

· User Percentage—Percentage of the user time.

· System Percentage—Percentage of the system time.

· I/O Wait Percentage—Percentage of the I/O wait time.

· Idle Percentage—Percentage of the idle time.

Paging

The Paging area contains the following fields:

· Paging In—Number pages that are paged in during the interval.

· Paging Out—Number pages that are paged out during the interval.

Connection State

· Established Connections—Number of established TCP connections.

· CLOSE_WAIT—Number of connections in CLOSE_WAIT state.

· TIME_WAIT—Number of connections in TIME_WAIT state.

Ping Test

When the polling interval expires, APM pings the AIX host by sending up to three ICMP packets. If APM receives a response packet, the ping succeeds and APM records the response time. If APM does not receive a response after sending out three ICMP packets, APM considers that the ping test has failed.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the AIX application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that APM sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the packets sent.

· Packets Received—Number of ICMP response packets that APM received in the last ping operation. The value is 0 or 1. Click the History Record icon to view the history graph of the packets received.

System Load

APM analyzes and displays the system load average for the monitored AIX in 1 minute, 5 minutes, and 15 minutes. System load average is the average number of processes running on the AIX system during a specific time period. Excessive system load can cause performance problems. The thresholds of system load vary by CPU type.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the average system load over the last 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the average system load over the last 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the average system load over the last 15 minutes.

System Call

The System Call area contains the following field:

· System Calls—Number of AIX system calls per second.

Process Count

The Process Count area contains the following fields:

· Active Process Count—Number of active processes in the AIX system.

· Non-Root Process—Number of non-root user processes.

· Await Resource Process—Number of processes that wait for resources.

File System Usage Ratio

The AIX file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system matches a physical disk partition or logical volume. The AIX application writes data to or reads data from the physical disk partition or logical volume by using the matching directory.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the AIX directory structure.

· File System Usage Ratio—Space usage ratio of the AIX file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the partition or logical volume. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the history graph of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval. Zombie processes in AIX do not have process names.

· ID—Unique identifier of the zombie process on the OS.

· Parent ID—ID of the parent process for the zombie process.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage.

· Memory Usage—Memory usage of the zombie process in the last polling interval. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

APM collects AIX traffic based on the IP address of the host where the application resides.

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by AIX over the last 1 hour.

· Today's Traffic—Total traffic sent and received by AIX since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of the network interface card in AIX. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of the network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of AIX network interface cards.

· Send Rate—Send rate of the network interface card in the last polling interval.

· Input Error Packet Rate—Number of inbound erroneous packets per second on the network interface card in the last polling interval.

· Output Error Packet Rate—Number of outbound erroneous packets per second on the network interface card in the last polling interval.

Error Log

APM examines the AIX error logs when APM polls AIX applications and displays the first 10 error logs obtained in the AIX application monitor report.

The Error Log area contains the following fields:

· Time—Time when the error occurred in the last polling interval.

· Log—Content of the error log in the last polling interval.

· More—Click More to view all error logs occurred in the last polling interval.

Process

By default, the list does not contain any processes. To monitor a process on AIX, click the Configuration icon to select the processes to be monitored. APM collects the index data including CPU usage and memory usage for the monitored processes when APM polls applications next time.

The Process area contains the following fields:

· Config—Click the Config icon to select the processes to be monitored in the monitor list window.

· Name—Name of the monitored process. APM can respectively collect index data for the processes that have the same name but different Process Identifiers (PIDs). You cannot view the history graph of index data for the processes that have the same name.

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process of the process.

· CPU Usage—CPU usage ratio of the monitored process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the CPU usage ratio for the monitored process.

¡ Click the History Record icon to view the history graph of the CPU usage ratio of the monitored process.

· Memory Usage—Memory usage ratio of the monitored process in the last polling interval. Click the History Record icon to view the history graph of the memory usage ratio of the monitored process.

· CPU Time—Duration that the process occupies the CPU in the last polling interval.

I/O State

APM can monitor the I/O status of the disk drivers in the AIX system.

The I/O State area contains the following fields:

· Device Name—Name of the disk drivers in the AIX system.

· I/O Rate—Size of the input/output data in the disk driver per second in the last polling interval.

· I/Os/Sec—Number of transfer times in the disk driver per second in the last polling interval. A transfer is an I/O request to the physical disk. Multiple logical requests can be integrated into a single I/O request to the disk. The size of the transferred data in each transfer is not fixed.

inode

An index node is called inode for short. The inodes are required when you create a file or directory in the AIX file system. If the inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system of the AIX application.

· Total—Total number of available inodes in the file system in the last polling interval. Click the History Record icon to view the history graph of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of idle inodes in the file system.

· In Use—Number of inodes that have been used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of used inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the inode usage ratio in the file system.

¡ Click the History Record icon to view the history graph of inode usage in the file system.

Session Information

The Session Information area displays AIX session login information.

The Session Information area contains the following fields:

· User Name—User logging in to the AIX application in the last polling interval.

· TTY—TTY used by the user.

· Login Time—Time when the user logged in to the AIX application.

· Idle—Idle time after the user logged in to the AIX application.

· Command—Most recently executed command after the user logged in to the AIX application.

Disk Mount

The Disk Mount area displays AIX disk mount information.

The Disk Mount area contains the following fields:

· Disk Name—Name of the disk.

· Disk State—Mount status of the disk.

· Disk Location—Location where the disk is mounted.

· Disk Description—Description of the disk.

Adapter

The Adapter area displays AIX adapter mount information.

The Adapter area contains the following fields:

· Adapter Name—Name of the adapter.

· Adapter State—Mount status of the adapter.

· Adapter Location—Location where the adapter is mounted.

· Adapter Description—Description of the adapter.

Cluster Information

The Cluster Information area displays AIX cluster information.

The Cluster Information area contains the following fields:

· Group Name—Name of the group to which each node in the cluster belongs.

· Status—Status of each node in the cluster.

· Node Name—Name of each node in the cluster.

MPIO

The MPIO area displays AIX MPIO information.

The MPIO area contains the following fields:

· MPIO State—Status of the MPIO.

· MPIO Device—Name of the destination device of the MPIO.

· MPIO Parent—Name of the source device of the MPIO.

Error Device Information

The Error Device Information area displays error information for the physical device where the OS is located.

The Error Device Information area contains the following fields:

· Identifier—ID of the error.

· Time—Time when the error occurred.

· Type—Severity of the error. Options are:

¡ P—The error might be caused by loss of devices or functional components, performance degradation, or corruption of hardware or software.

¡ T—The error is temporary and has been eliminated after retries.

¡ I—The message is an informational message. No error occurred.

¡ U—The severity of the error is unknown.

· Class—Source of the error. Options are:

¡ H—Hardware or media failure.

¡ S—Software failure.

¡ O—Human error.

¡ U—Unknown.

· Resource Name—Name of the resource where the error occurred.

· Description—Description of the error.

Memory Info

The Memory Info area contains the following fields:

· Memory Serial Number—Serial number of the memory card on the AIX server.

· Memory Size—Size of the memory.

· Location—Memory card position on the server.

Thermal

The Thermal area contains the following fields:

· Thermal Sensor—Name of the thermal sensor on the AIX server.

· Degrees—Temperature of the server, in degrees Celsius.

· Status—Temperature status of the server.

· Location—Thermal sensor position on the server.

Fan Speed

The Fan Speed area contains the following fields:

· Fan Sensor—Name of the fan sensor on the AIX server.

· Fan Speed—Fan speed of the server

· Status—Fan status of the server.

· Location—Fan sensor position on the server.

Processor Info

The Processor Info area contains the following fields:

· Processor Name—Name of the CPU processor on the AIX server.

· Processor State—Status of the CPU processor.

· Position—CPU processor position on the server.

· Description—Description of the CPU processor.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product that the board applies to.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

SCO UNIX

SCO UNIX is a UNIX operating system developed by SCO.

Adding an SCO UNIX application monitor

APM can monitor SCO UNIX through CLI. When you add application monitors for SCO UNIX, follow these guidelines:

· Enable and configure Telnet or SSH on SCO UNIX. For information about enabling Telnet or SSH on SCO UNIX, see the SCO UNIX configuration guide.

· Obtain the username and password of the Telnet or SSH user who has the SCO UNIX administrator's privileges.

· Add SCO UNIX hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the SCO UNIX application, make sure at least one probe is configured in APM. After an SCO UNIX application monitor is added, APM sends the IP address of the monitored SCO UNIX application to the probes for traffic collection.

To add an SCO UNIX application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

¡ From the navigation tree, select Application Manager > Application Monitor. In the application monitor list, click Add.

The Add Application page displays all application types that can be monitored by APM.

3. Click SCO UNIX of the UNIX Server Monitor class.

The page for adding an SCO UNIX application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the SCO UNIX application to be monitored is installed. APM automatically checks the IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Monitor Type—Select the protocol (SSH or Telnet) through which APM monitors the SCO UNIX application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on SCO UNIX.

- Username—Enter the SSH username. The user must have the SCO UNIX administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on SCO UNIX.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from SCO UNIX. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from SCO UNIX within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the SCO UNIX host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on SCO UNIX.

- Username—Enter the Telnet username. The user must have the SCO UNIX administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from Solaris. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from SCO UNIX within the timeout time, APM considers that the interaction has failed.

¡ Contact—Enter the contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor. This field is available only when you select Disable from the Use Template list.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of SCO UNIX applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that SCO UNIX depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the SCO UNIX application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

5. Click OK.

Modifying an SCO UNIX application monitor

Authorized users can modify all parameters except the IP address and the APM server for an SCO UNIX application monitor. When the IP address of a monitored SCO UNIX host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify an SCO UNIX application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the Modify icon for the SCO UNIX application monitor you want to modify.

The page for modifying the SCO UNIX application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding an SCO UNIX application monitor."

5. Click OK.

Viewing the SCO UNIX application monitor report

After an SCO UNIX application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for SCO UNIX by viewing the monitor report.

To access the SCO UNIX application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of an SCO UNIX application monitor to display the report.

Figure 54 shows part of an SCO UNIX monitor report.

Figure 54 Part of an SCO UNIX application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored SCO UNIX application.

· IP Address—IP address of the SCO UNIX host.

· Application Type—Type of the monitored application, -which is always SCO UNIX.

· Version—Version of the SCO UNIX operating system.

· System Running Time—Duration since the startup of the SCO UNIX application to the time when APM last polled the SCO UNIX application.

· Last Polling Time—Time when APM last polled the SCO UNIX application.

· Relationship—Click the Relationship icon to view dependencies between the SCO UNIX application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the SCO UNIX host. If no alarm is generated by the SCO UNIX application, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the SCO UNIX application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the SCO UNIX application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the SCO UNIX application in the last 30 days.

· Available Time—Total amount of time that the SCO UNIX application was available after 00:00 today.

· Unavailable Time—Total amount of time that the SCO UNIX application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the SCO UNIX application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the SCO UNIX application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage—CPU usage ratio of the SCO UNIX application in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical memory—Physical memory of the SCO UNIX application, which corresponds to the physical memory bar.

· Swap—Swap memory of the SCO UNIX application, which corresponds to the disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Amount of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the memory (including physical memory and swap memory) usage.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the SCO UNIX host by sending up to three ICMP packets. If APM receives a response packet, the ping succeeds and APM records the response time. If APM does not receive a response after sending out three ICMP packets, APM considers that the ping test has failed.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the AIX application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that APM sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the packets sent.

System Load

APM analyzes and displays the system load average for the monitored SCO UNIX application in 1 minute, 5 minutes, and 15 minutes. System load average is the average number of processes running on the SCO UNIX system during a specific time period. Excessive system load can cause performance problems. The thresholds of system load vary by CPU type.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the system load over the last 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the system load over the last 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the system load over the last 15 minutes.

File System Usage Ratio

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the SCO UNIX directory structure.

· File System Usage—Space usage of the SCO UNIX file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· Used Space—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the partition or logical volume. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the history graph of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval. Zombie processes in SCO UNIX do not have process names.

· Process ID—Unique identifier of the zombie process on the OS.

· Parent ID—ID of the parent process for the zombie process.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

APM collects SCO UNIX traffic based on the IP address of the host where the application is located.

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by SCO UNIX over the last 1 hour.

· Today's Traffic—Total traffic sent and received by SCO UNIX since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of the network interface card in SCO UNIX.

· Receive Rate—Receive rate of the network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of SCO UNIX network interface cards.

· Send Rate—Send rate of the network interface card in the last polling interval.

· Error Packet Receive Rate—Number of inbound erroneous packets per second on the network interface card in the last polling interval.

· Error Packet Send Rate—Number of outbound erroneous packets per second on the network interface card in the last polling interval.

inode

Index nodes (inodes) are required when you create a file or directory in the SCO UNIX file system. If the inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system of the SCO UNIX application.

· Total inodes—Total number of available inodes in the file system in the last polling interval. Click the History Record icon to view the history graph of the total number of inodes in the file system.

· Free inodes—Number of inodes that are not used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of idle inodes in the file system.

· Used inodes—Number of inodes that have been used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of used inodes in the file system.

· Usage—Usage of inodes in the file system in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the inode usage in the file system.

¡ Click the History Record icon to view the history graph of the inode usage in the file system.

Process

By default, the list does not contain any processes. To monitor a process on SCO UNIX, click the Configuration icon to select the processes to be monitored. APM collects the index data including CPU usage for the monitored processes when APM polls applications next time.

The Process area contains the following fields:

· Config—Click the Config icon to select the processes to be monitored in the monitor list window.

· Process Name—Name of the monitored process. APM can respectively collect CPU usage and memory usage for the processes that have the same name but different PIDs.

· Process ID—Unique identifier of the monitored process on the OS.

· Parent ID—ID of the parent process of the monitored process.

· CPU Usage—CPU usage ratio of the monitored process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the CPU usage ratio for the monitored process.

¡ Click the History Record icon to view the history graph of the CPU usage ratio of the monitored process.

· CPU Time—Duration that the process occupies the CPU in the last polling interval.

Session Information

The Session Information area displays SCO UNIX session login information.

The Session Information area contains the following fields:

· Username—User logging in to the SCO UNIX application in the last polling interval.

· TTY—TTY used by the user.

· Login Time—Time when the user logged in to the SCO UNIX application.

· Login IP—Client IP address used when the user logged in to SCO UNIX.

· Idle—Idle time after the user logged in to the SCO UNIX application.

· Command—Most recently executed command after the user logged in to the SCO UNIX application.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

Solaris

Solaris can be installed on the servers with x86 or SPARC processors. The performance and stability of Solaris greatly affects the performance of applications or services running on it.

Adding a Solaris application monitor

APM monitors Solaris applications through SNMP or CLI. When you add Solaris application monitors, follow these guidelines:

· To monitor Solaris applications through SNMP, enable SNMP on Solaris and obtain read-only and read-write community strings. For information about enabling SNMP on Solaris, see the Solaris online help.

· To monitor Solaris applications through CLI, enable Telnet or SSH on Solaris and obtain the username and password of the Telnet or SSH user who has the Solaris administrator's privileges. For information about enabling Telnet or SSH on Solaris, see the Solaris configuration guide.

· Add Solaris hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the Solaris application, make sure at least one probe is configured in APM. After a Solaris application monitor is added, APM sends the IP address of the monitored Solaris application to the probes for traffic collection.

To add a Solaris application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

¡ From the navigation tree, select Application Manager > Application Monitor. In the application monitor list, click Add.

The Add Application page displays all application types that can be monitored by APM.

3. Click Solaris of the UNIX Server Monitor class.

The page for adding a Solaris application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the Solaris application to be monitored is installed. APM automatically checks the IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Monitor Type—Select the protocol (SSH, Telnet, or SNMP) through which APM monitors the Solaris application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SNMP is selected, configure the following parameters:

- Edit SNMP Parameters—Select this option if you want to manually configure SNMP parameters for APM. Make sure the SNMP settings are the same as those on Solaris.

- Parameter Type—Select the SNMP parameter type. Options are SNMPv1, SNMPv2c, and SNMPv3 Template. The SNMPv3 Template option is available only when Select an Existing Template is selected.

- Read-Only Community String—Enter the SNMP read-only community string, with which APM can read MIB variables from the Solaris host.

- Read-Write Community String—Enter the read-write SNMP community string, with which APM can read MIB variables from or write MIB variables to the Solaris host.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for an SNMP response from Solaris. The value range is 1 to 60 seconds and the default is 4 seconds. If no SNMP response is received from Solaris within the timeout period, APM considers that the interaction has failed.

- Retries (1-20)—Enter how many times APM retries to send SNMP packets to the Solaris host.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on Solaris.

- Username—Enter the SSH username. The user must have the Solaris administrator's privileges.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on Solaris.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from Solaris. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from Solaris within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the Solaris host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on Solaris.

- Username—Enter the Telnet username. The user must have the Solaris administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from Solaris. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from Solaris within the timeout time, APM considers that the interaction has failed.

¡ Contact—Enter user contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of Solaris applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that Solaris depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the Solaris application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

5. Click OK.

Modifying a Solaris application monitor

Authorized users can modify all parameters except the IP address and the APM server for a Solaris application monitor. When the IP address of a monitored Solaris host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a Solaris application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click the Modify icon for the Solaris application monitor you want to modify.

The page for modifying the Solaris application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a Solaris application monitor."

5. Click OK.

Viewing the Solaris application monitor report

After a Solaris monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for Solaris by viewing the monitor report.

To access the Solaris application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a Solaris application monitor to display the report.

Figure 55 shows part of a Solaris monitor report.

Figure 55 Part of a Solaris application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored Solaris application.

· IP Address—IP address of the Solaris host.

· Application Type—Type of the monitored application, which is always Solaris.

· Version—Version of the Solaris operating system.

· System Running Time—Duration since the startup of the Solaris application to the time when APM last polled the Solaris application.

· Last Polling Time—Time when APM last polled the Solaris application.

· Relationship—Click the Relationship icon to view dependencies between the Solaris application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the Solaris host. If no alarm is generated by Solaris, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the Solaris application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the Solaris application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the Solaris application in the last 30 days.

· Available Time—Total amount of time that the Solaris application was available after 00:00 today.

· Unavailable Time—Total amount of time that the Solaris application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the Solaris application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the Solaris application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the Solaris application in the last APM polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the Solaris application, which corresponds to the physical memory bar.

· Swap—Swap memory of the Solaris application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the Solaris host by sending up to three ICMP packets. If APM receives a response packet, the ping succeeds and APM records the response time. If APM does not receive a response after sending out three ICMP packets, APM considers that the ping test has failed.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the Solaris application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that APM sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

· Packets Received—Number of ICMP response packets that APM received in the last ping operation. The value is 0 or 1. Click the History Record icon to view the history graph of the received packets.

System Load

APM analyzes and displays the system load average for the monitored Solaris application in 1 minute, 5 minutes, and 15 minutes. System load average is the average number of processes running on the Solaris system during a specific time period. Excessive system load can cause performance problems. The thresholds of system load vary by CPU type.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the average system load in 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the average system load in 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the average system load in 15 minutes.

File System Usage Ratio

The Solaris file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. The Solaris application writes data to or reads data from the physical disk partition or logical volume by using the corresponding directory.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the Solaris directory structure.

· File System Usage Ratio—Space usage ratio of the Solaris file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system partition or logical volume. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the history graph of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval.

· ID—ID of the zombie process in the last polling interval.

· Parent ID—ID of the parent process for the zombie process in the last polling interval.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory Usage—Memory usage of the zombie process in the last polling interval. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by Solaris over the last 1 hour.

· Today's Traffic—Total traffic sent and received by Solaris since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of the network interface card in Solaris. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of the network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of Solaris network interface cards.

· Send Rate—Send rate of the network interface card in the last APM polling interval.

· Input Error Packet Rate—Number of inbound erroneous packets per second on the network interface card in the last polling interval

· Output Error Packet Rate—Number of outbound erroneous packets per second on the network interface card in the last polling interval.

Session Information

The Session Information area displays Solaris session login information.

The Session Information area contains the following fields:

· User Name—User logging in to Solaris in the last interval.

· TTY—TTY used by the user.

· Login IP—Client IP address used when the user logged in to Solaris.

· Login Time—Time when the user logged in to Solaris.

· Idle—Idle time after the user logged in to Solaris.

· Command—Most recently executed command after the user logged in to Solaris.

Process

By default, the list does not contain any processes. To monitor processes on Solaris, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select the processes to be monitored in the monitor list window.

· Process Name—Name of the monitored process. APM can separately collect index data for the processes that have the same name but different Process Identifiers (PIDs).

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process of the process.

· CPU Usage—CPU usage ratio of the monitored process in the last polling interval.

¡ Click the Threshold setting icon to set alarm thresholds of the CPU usage ratio for the monitored process.

¡ Click the History Record icon to view the history graph of the CPU usage ratio of the monitored process.

· Memory Usage—Memory usage ratio of the monitored process in the last APM polling interval. Click the History Record icon to view the history graph of the memory usage ratio of the monitored process.

· CPU Time—Duration that the process occupies the CPU in the last polling interval.

I/O State

APM can monitor the I/O status of the disk drivers in the Solaris system.

The I/O State area contains the following fields:

· Device Name—Name of the disk drivers in the Solaris system.

· I/O Read Rate—Size of the output data in the disk driver per second in the last polling interval.

· I/O Write Rate—Size of the input data in the disk driver per second in the last polling interval.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

FreeBSD

FreeBSD's performance and stability can greatly affect the performance of applications or services running on it.

Adding a FreeBSD application monitor

APM monitors FreeBSD applications through CLI. When you add FreeBSD application monitors, follow these guidelines:

· Enable Telnet or SSH on FreeBSD. For more information enabling Telnet or SSH on FreeBSD, see the FreeBSD configuration guide.

· Obtain the username and password of the Telnet or SSH user who has the FreeBSD administrator's privileges

· Add FreeBSD hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the FreeBSD application, make sure at least one probe is configured in APM. After a FreeBSD application monitor is added, APM sends the IP address of the monitored FreeBSD application to the probes for traffic collection.

To add a FreeBSD application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

¡ From the navigation tree, select Application Manager > Application Monitor. In the application monitor list, click Add.

The Add Application page displays all application types that can be monitored by APM.

3. Click FreeBSD of the UNIX Server Monitor class.

The page for adding a FreeBSD application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the FreeBSD application to be monitored is installed. APM automatically checks the IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor to aid maintenance.

¡ Monitor Type—Select the protocol (SSH or Telnet) through which APM monitors the FreeBSD application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on FreeBSD.

- Username—Enter the SSH username. The user must have the FreeBSD administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on FreeBSD.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from FreeBSD. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from FreeBSD within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the FreeBSD host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on FreeBSD.

- Username—Enter the Telnet username. The user must have the FreeBSD administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from FreeBSD. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from FreeBSD within the timeout time, APM considers that the interaction has failed.

¡ Contact—Enter user contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of FreeBSD applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that FreeBSD depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the FreeBSD application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

5. Click OK.

Modifying a FreeBSD application monitor

Authorized users can modify all parameters except the IP address and the APM server for a FreeBSD application monitor. When the IP address of a monitored FreeBSD host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a FreeBSD application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click the Modify icon for the FreeBSD application monitor you want to modify.

The page for modifying the FreeBSD application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a FreeBSD application monitor."

5. Click OK.

Viewing the FreeBSD application monitor report

After a FreeBSD application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for FreeBSD by viewing the monitor report.

To access the FreeBSD application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a FreeBSD application monitor to display the report.

Figure 56 shows part of a FreeBSD monitor report.

Figure 56 Part of a FreeBSD application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored FreeBSD application.

· IP Address—IP address of the FreeBSD host.

· Application Type—Type of the monitored application, which is always FreeBSD.

· Version—Version of the FreeBSD operating system.

· System Running Time—Duration since the startup of the FreeBSD application to the time when APM last polled the FreeBSD application.

· Last Polling Time—Time when APM last polled the FreeBSD application.

· Relationship—Click the Relationship icon to view dependencies between the FreeBSD application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the FreeBSD host. If no alarm is generated by FreeBSD, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the FreeBSD application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the FreeBSD application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the FreeBSD application in the last 30 days.

· Available Time—Total amount of time that the FreeBSD application was available after 00:00 today.

· Unavailable Time—Total amount of time that the FreeBSD application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the FreeBSD application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the FreeBSD application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the FreeBSD application in the last APM polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the FreeBSD application, which corresponds to the physical memory bar.

· Swap—Swap memory of the FreeBSD application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the FreeBSD host by sending up to three ICMP packets. If APM receives a response packet, the ping succeeds and APM records the response time. If APM does not receive a response after sending out three ICMP packets, APM considers that the ping test has failed.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the FreeBSD application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that are sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

· Packets Received—Number of ICMP response packets that are received in the last ping operation. The value is 0 or 1. Click the History Record icon to view the history graph of the received packets.

System Load

APM analyzes and displays the system load average for the monitored FreeBSD application in 1 minute, 5 minutes, and 15 minutes. System load average is the average number of processes running on the FreeBSD system during a specific time period. Excessive system load can cause performance problems. The thresholds of system load vary by CPU type.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the average system load in 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the average system load in 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the average system load in 15 minutes.

File System Usage Ratio

The FreeBSD file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. The FreeBSD application writes data to or reads data from the physical disk partition or logical volume by using the corresponding directory.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the FreeBSD directory structure.

· File System Usage Ratio—Space usage ratio of the FreeBSD file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system in the last polling interval. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system partition or logical volume in the last polling interval. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the change trend of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval.

· ID—ID of the zombie process in the last polling interval.

· Parent ID—ID of the parent process for the zombie process in the last polling interval.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory Usage—Memory usage of the zombie process in the last polling interval. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by FreeBSD over the last 1 hour.

· Today's Traffic—Total traffic sent and received by FreeBSD since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of the network interface card in FreeBSD. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of the network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of FreeBSD network interface cards.

· Send Rate—Send rate of a network interface card in the last polling interval.

· Input Error Packet Rate—Number of inbound erroneous packets per second on the network interface card in the last polling interval.

· Output Error Packet Rate—Number of outbound erroneous packets per second on the network interface card in the last polling interval.

inode

Index nodes (inodes) are required when you create a file or directory in the FreeBSD file system. If the inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system on the FreeBSD server.

· Total—Total number of available inodes in the file system in the last polling interval. Click the History Record icon to view the history graph of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of idle inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the inode usage in the file system.

¡ Click the History Record icon to view the history graph of inode usage in the file system.

Process

By default, the list does not contain any processes. To monitor a process on FreeBSD, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select the processes to be monitored in the monitor list window.

· Process—Name of the monitored process. APM can respectively collect monitored data for the processes that have the same name but different Process Identifiers (PIDs).

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process of the process.

· CPU Usage—CPU usage ratio of the monitored process in the last polling interval.

¡ Click the Threshold setting icon to set alarm thresholds of the CPU usage ratio for the monitored process.

¡ Click the History Record icon to view the history graph of the CPU usage ratio of the monitored process.

· Memory Usage—Memory usage ratio of the monitored process in the last polling interval. Click the History Record icon to view the history graph of the memory usage ratio of the monitored process.

· CPU Time—Duration that the process occupies the CPU in the last polling interval.

I/O State

APM can monitor the I/O status of the disk drivers in the FreeBSD system.

The I/O State area contains the following fields:

· Device Name—Name of the disk drivers in the FreeBSD system.

· I/O Read Rate—Size of the output data in the disk driver per second in the last polling interval.

· I/O Write Rate—Size of the input data in the disk driver per second in the last polling interval.

Session Information

The Session Information area displays FreeBSD session login information.

The Session Information area contains the following fields:

· User Name—User logging in to FreeBSD in the last polling interval.

· TTY—TTY used by the user.

· Login IP—Client IP address used when the user logged in to FreeBSD.

· Login Time—Time when the user logged in to FreeBSD.

· Idle—Idle time after the user logged in to FreeBSD.

· Command—Most recently executed command after the user logged in to FreeBSD.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

Mac OS

The performance and stability of Apple's Mac OS can greatly affect the performance of applications or services running on it.

Adding a Mac OS application monitor

APM monitors Mac OS applications through SNMP or CLI. When you add Mac OS application monitors, follow these guidelines:

· To monitor the Mac OS application through SNMP, enable SNMP on Mac OS and obtain read-only and read-write community strings. For information about enabling SNMP on Mac OS, see the Mac OS online help.

· To monitor the Mac OS application through CLI, enable Telnet or SSH on Mac OS and obtain the username and password of the Telnet or SSH user who has the Mac OS administrator's privileges. For information about enabling Telnet or SSH on Mac OS, see the Mac OS configuration guide.

· Add Mac OS hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the Mac OS application, make sure at least one probe is configured in APM. After a Mac OS application monitor is added, APM sends the IP address of the monitored Mac OS application to the probes for traffic collection.

To add a Mac OS application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click Mac OS of the UNIX Server Monitor class.

The page for adding a Mac OS application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the Mac OS application to be monitored is installed. APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor to aid maintenance.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval provides more accurate realtime data, but consumes more system resources. This field is available only when you select Disable from the Use Template list.

¡ Monitor Type—Select the protocol (SSH, Telnet, or SNMP) through which APM monitors the Mac OS application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SNMP is selected, configure the following parameters:

- Edit SNMP Parameters—Select this option if you want to manually configure SNMP parameters for APM. Make sure the SNMP settings are the same as those on Mac OS.

- Parameter Type—Select the SNMP parameter type. Options are SNMPv1, SNMPv2c, and SNMPv3 Template. The SNMPv3 Template option is available only when Select an Existing Template is selected.

- Read-Only Community String—Enter the SNMP read-only community string, with which APM can read MIB variables from the Mac OS host.

- Read-Write Community String—Enter the read-write SNMP community string, with which APM can read MIB variables from or write MIB variables to the Mac OS host.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for an SNMP response from Mac OS. The value range is 1 to 60 seconds and the default is 4 seconds. If no SNMP response is received from Mac OS within the timeout time, APM considers that the interaction has failed.

- Retries (1-20)—Enter how many times APM retries to send SNMP packets to the Mac OS host.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on Mac OS.

- Username—Enter the SSH username. The user must have the Mac OS administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on Mac OS.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from Mac OS. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from Mac OS within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the Mac OS host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on Mac OS.

- Username—Enter the Telnet username. The user must have the Mac OS administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from Mac OS. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from Mac OS within the timeout time, APM considers that the interaction has failed.

¡ Contact—Enter user contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of Mac OS applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that Mac OS depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the Mac OS application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the connection.

5. Click OK.

Modifying a Mac OS application monitor

Authorized users can modify all parameters except the IP address and the APM server for a Mac OS application monitor. When the IP address of a monitored Mac OS host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a Mac OS application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click the Modify icon for the Mac OS application monitor you want to modify.

The page for modifying the Mac OS application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a Mac OS application monitor."

5. Click OK.

Viewing the Mac OS application monitor report

After a Mac OS application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for Mac OS by viewing the monitor report.

To access the Mac OS application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a Mac OS application monitor to display the report.

Figure 57 shows part of a Mac OS monitor report.

Figure 57 Part of a Mac OS application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored Mac OS application.

· IP Address—IP address of the Mac OS host.

· Application Type—Type of the monitored application, which is always Mac OS.

· Version—Version of the Mac OS application.

· System Running Time—Duration since the startup of the Mac OS application to the time when APM last polled the Mac OS application.

· Last Polling Time—Time when APM last polled the Mac OS application.

· Relationship—Click the Relationship icon to view dependencies between the Mac OS application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the Mac OS host. If no alarm is generated by Mac OS, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the Mac OS application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the Mac OS application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the Mac OS application in the last 30 days.

· Available Time—Total amount of time that the Mac OS application was available after 00:00 today.

· Unavailable Time—Total amount of time that the Mac OS application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the Mac OS application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the Mac OS application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the Mac OS application in the last APM polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the Mac OS application, which corresponds to the physical memory bar.

· Swap—Swap memory of the Mac OS application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the Mac OS host by sending up to three ICMP packets. If APM receives a response packet, the ping succeeds and APM records the response time. If APM does not receive a response after sending out three ICMP packets, APM considers that the ping test has failed.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the Mac OS application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that are sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

System Load

APM analyzes and displays the system load average for the monitored Mac OS application in 1 minute, 5 minutes, and 15 minutes. System load average is the average number of processes running on the Mac OS system during a specific time period. Excessive system load can cause performance problems. The thresholds of system load vary by CPU type.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the average system load in 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the average system load in 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the average system load in 15 minutes.

File System Usage Ratio

The Mac OS file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. The Mac OS application writes data to or reads data from the physical disk partition or logical volume by using the corresponding directory.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the Mac OS directory structure.

· File System Usage Ratio—Space usage ratio of the file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system partition or logical volume. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the change trend of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval.

· ID—ID of the zombie process in the last polling interval.

· Parent ID—ID of the parent process for the zombie process in the last polling interval.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory Usage—Memory usage of the zombie process in the last polling interval. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by Mac OS over the last 1 hour.

· Today's Traffic—Total traffic sent and received by Mac OS since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of the network interface card in Mac OS. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of the network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of Mac OS network interface cards.

· Send Rate—Send rate of the network interface card in the last polling interval.

· Input Error Packet Rate—Number of inbound erroneous packets per second on the network interface card in the last polling interval.

· Output Error Packet Rate—Number of outbound erroneous packets per second on the network interface card in the last polling interval.

inode

Index nodes (inodes) are required when you create a file or directory in the Mac OS file system. If inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system on the Mac OS server.

· Total—Total number of available inodes in the file system in the last polling interval. Click the History Record icon to view the history graph of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of idle inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the inode usage in the file system.

¡ Click the History Record icon to view the history graph of inode usage in the file system.

Process

By default, the list does not contain any processes. To monitor a process on Mac OS, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select the processes to be monitored in the monitor list window.

· Process—Name of the monitored process. APM can separately collect monitored data for the processes that have the same name but different Process Identifiers (PIDs).

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process of the process.

· CPU Usage—CPU usage ratio of the monitored process in the last polling interval.

¡ Click the Threshold setting icon to set alarm thresholds of the CPU usage ratio for the monitored process.

¡ Click the History Record icon to view the history graph of the CPU usage ratio of the monitored process.

· Memory Usage—Memory usage ratio of the monitored process in the last polling interval. Click the History Record icon to view the history graph of the memory usage ratio of the monitored process.

· CPU Time—Duration that the process occupies the CPU in the last polling interval.

I/O State

APM can monitor the I/O status of the disk drivers in the Mac OS system.

The I/O State area contains the following fields:

· Device Name—Name of the disk driver in the Mac OS system.

· I/O Rate—Size of the input/output data in the disk driver per second in the last polling interval.

· Transfers/Sec—Number of transfer times in the disk driver per second in the last polling interval. A transfer is represented by an I/O request to the physical disk. Multiple logical requests can be integrated into a single I/O request to the disk. The size of the transferred data in each transfer is not fixed.

Session Information

The Session Information area displays Mac OS session login information.

The Session Information area contains the following fields:

· User Name—User logging in to Mac OS in the last polling interval.

· TTY—TTY used by the user.

· Login IP—Client IP address used when the user logged in to Mac OS.

· Login Time—Time when the user logged in to Mac OS.

· Idle—Idle time after the user logged in to Mac OS.

· Command—Most recently executed command after the user logged in to Mac OS.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

OpenBSD

OpenBSD's performance and stability greatly affects the performance of applications running on it.

Adding an OpenBSD application monitor

APM monitors OpenBSD applications through CLI. When you add OpenBSD application monitors, follow these guidelines:

· Enable Telnet or SSH on OpenBSD. For more information about enabling Telnet or SSH on OpenBSD, see the OpenBSD configuration guide.

· Obtain the username and password of the Telnet or SSH user who has the OpenBSD administrator's privileges.

· Add OpenBSD hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the OpenBSD application, make sure at least one probe is configured in APM. After an OpenBSD application monitor is added, APM sends the IP address of the monitored OpenBSD application to the probes for traffic collection.

To add an OpenBSD application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click OpenBSD of the UNIX Server Monitor class.

The page for adding an OpenBSD application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the OpenBSD application to be monitored is installed. APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor to aid maintenance.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval provides more accurate realtime data, but consumes more system resources. This field is available only when you select Disable from the Use Template list.

¡ Monitor Type—Select the protocol (SSH or Telnet) through which APM monitors the OpenBSD application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on OpenBSD.

- Username—Enter the SSH username. The user must have the OpenBSD administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on OpenBSD.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from OpenBSD. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from OpenBSD within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the OpenBSD host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on OpenBSD.

- Username—Enter the Telnet username. The user must have the OpenBSD administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from OpenBSD. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from OpenBSD within the timeout time, APM considers that the interaction has failed.

¡ Contact—Enter user contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of OpenBSD applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that OpenBSD depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the OpenBSD application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the connection.

5. Click OK.

Modifying an OpenBSD application monitor

Authorized users can modify all parameters except the IP address and the APM server for an OpenBSD application monitor. When the IP address of a monitored OpenBSD host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify an OpenBSD application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click the Modify icon for the OpenBSD application monitor you want to modify.

The page for modifying the OpenBSD application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding an OpenBSD application monitor."

5. Click OK.

Viewing the OpenBSD application monitor report

After an OpenBSD application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for OpenBSD by viewing the monitor report.

To access the OpenBSD application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of an OpenBSD application monitor to display the report.

Figure 58 shows part of an OpenBSD monitor report.

Figure 58 Part of an OpenBSD application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored OpenBSD application.

· IP Address—IP address of the OpenBSD host.

· Application Type—Type of the monitored application, which is always OpenBSD.

· Version—Version of the OpenBSD application.

· System Running Time—Duration since the startup of the OpenBSD application to the time when APM last polled the OpenBSD application.

· Last Polling Time—Time when APM last polled the OpenBSD application.

· Relationship—Click the Relationship icon to view dependencies between the OpenBSD application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the OpenBSD host. If no alarm is generated by OpenBSD, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the OpenBSD application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the OpenBSD application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the OpenBSD application in the last 30 days.

· Available Time—Total amount of time that the OpenBSD application was available after 00:00 today.

· Unavailable Time—Total amount of time that the OpenBSD application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the OpenBSD application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the OpenBSD application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the OpenBSD application in the last APM polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the OpenBSD application, which corresponds to the physical memory bar.

· Swap—Swap memory of the OpenBSD application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the OpenBSD host by sending up to three ICMP packets. If APM receives a response packet, the ping succeeds and APM records the response time. If APM does not receive a response after sending out three ICMP packets, APM considers that the ping test has failed.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the OpenBSD application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that are sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

System Load

APM analyzes and displays the system load average for the monitored OpenBSD application in 1 minute, 5 minutes, and 15 minutes. System load average is the average number of processes running on the OpenBSD system during a specific time period. Excessive system load can cause performance problems. The thresholds of system load vary by CPU type.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the average system load in 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the average system load in 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the average system load in 15 minutes.

File System Usage Ratio

The OpenBSD file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. The OpenBSD application writes data to or reads data from the physical disk partition or logical volume by using the corresponding directory.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the OpenBSD directory structure.

· File System Usage Ratio—Space usage ratio of the file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system partition or logical volume. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the change trend of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval.

· ID—ID of the zombie process in the last polling interval.

· Parent ID—ID of the parent process for the zombie process in the last polling interval.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory Usage—Memory usage of the zombie process in the last polling interval. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by OpenBSD over the last 1 hour.

· Today's Traffic—Total traffic sent and received by OpenBSD since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of the network interface card in OpenBSD. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of the network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of OpenBSD network interface cards.

· Send Rate—Send rate of a network interface card in the last polling interval.

· Input Error Packet Rate—Number of inbound erroneous packets per second on the network interface card in the last polling interval.

· Output Error Packet Rate—Number of outbound erroneous packets per second on the network interface card in the last polling interval.

inode

Index nodes (inodes) are required when you create a file or directory in the OpenBSD file system. If the inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system on the OpenBSD server.

· Total—Total number of available inodes in the file system in the last polling interval. Click the History Record icon to view the history graph of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of idle inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the inode usage in the file system.

¡ Click the History Record icon to view the history graph of inode usage in the file system.

Process

By default, the list does not contain any processes. To monitor a process on OpenBSD, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select the processes to be monitored in the monitor list window.

· Process—Name of the monitored process. APM can respectively collect monitored data for the processes that have the same name but different Process Identifiers (PIDs).

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process of the process.

· CPU Usage—CPU usage ratio of the monitored process in the last polling interval.

¡ Click the Threshold setting icon to set alarm thresholds of the CPU usage ratio for the monitored process.

¡ Click the History Record icon to view the history graph of the CPU usage ratio of the monitored process.

· Memory Usage—Memory usage ratio of the monitored process in the last polling interval. Click the History Record icon to view the history graph of the memory usage ratio of the monitored process.

· CPU Time—Duration that the process occupies the CPU in the last polling interval.

I/O State

APM can monitor the I/O status of the disk drivers in the OpenBSD system.

The I/O State area contains the following fields:

· Device Name—Name of the disk drivers in the OpenBSD system.

· I/O Rate—Size of the input/output data in the disk driver per second in the last polling interval.

· Transfers/Sec—Number of transfer times in the disk driver per second in the last polling interval. A transfer is an I/O request to the physical disk. Multiple logical requests can be integrated into a single I/O request to the disk. The size of the transferred data in each transfer is not fixed.

Session Information

The Session Information area displays OpenBSD session login information.

The Session Information area contains the following fields:

· User Name—User logging in to OpenBSD in the last polling interval.

· TTY—TTY used by the user.

· Login IP—Client IP address used when the user logged in to OpenBSD.

· Login Time—Time when the user logged in to OpenBSD.

· Idle—Idle time after the user logged in to OpenBSD.

· Command—Most recently executed command after the user logged in to OpenBSD.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

HP-UX

HP-UX's performance and stability affects the performance of applications running on it. APM provides the ability to monitor HP-UX 11.00 or later versions of the operating system.

Adding an HP-UX application monitor

APM monitors HP-UX applications through CLI. When you add HP-UX application monitors, follow these guidelines:

· Enable Telnet or SSH on HP-UX. For more information about enabling Telnet or SSH on HP-UX, see the HP-UX configuration guide.

· Obtain the username and password of the Telnet or SSH user who has the HP-UX administrator's privileges.

· Add HP-UX hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the HP-UX application, make sure at least one probe is configured in APM. After an HP-UX application monitor is added, APM sends the IP address of the monitored HP-UX application to the probes for traffic collection.

To add an HP-UX application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click HP-UX of the UNIX Server Monitor class.

The page for adding an HP-UX application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the HP-UX application to be monitored is installed. APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor to aid maintenance.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval provides more accurate realtime data, but consumes more system resources. This field is available only when you select Disable from the Use Template list.

¡ Monitor Type—Select the protocol (SSH or Telnet) through which APM monitors the HP-UX application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on HP-UX.

- Username—Enter the SSH username. The user must have the HP-UX administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on HP-UX.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from HP-UX. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from HP-UX within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the HP-UX host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on HP-UX.

- Username—Enter the Telnet username. The user must have the HP-UX administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from HP-UX. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from HP-UX within the timeout time, APM considers that the interaction has failed.

¡ Contact—Enter user contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of HP-UX applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that HP-UX depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the HP-UX application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the connection.

5. Click OK.

Modifying an HP-UX application monitor

Authorized users can modify all parameters except the IP address and the APM server for an HP-UX application monitor. When the IP address of a monitored HP-UX host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify an HP-UX application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click the Modify icon for the HP-UX application monitor you want to modify.

The page for modifying the HP-UX application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding an HP-UX application monitor."

5. Click OK.

Viewing the HP-UX application monitor report

After an HP-UX application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for HP-UX by viewing the monitor report.

To access the HP-UX application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of an HP-UX application monitor to display the report.

Figure 59 shows part of an HP-UX monitor report.

Figure 59 Part of an HP-UX application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored HP-UX application.

· IP Address—IP address of the HP-UX host.

· Application Type—Type of the monitored application, which is always HP-UX.

· Version—Version of the HP-UX application.

· System Running Time—Duration since the startup of the HP-UX application to the time when APM last polled the HP-UX application.

· Last Polling Time—Time when APM last polled the HP-UX application.

· Relationship—Click the Relationship icon to view dependencies between the HP-UX application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the HP-UX host. If no alarm is generated by HP-UX, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the HP-UX application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the HP-UX application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the HP-UX application in the last 30 days.

· Available Time—Total amount of time that the HP-UX application was available after 00:00 today.

· Unavailable Time—Total amount of time that the HP-UX application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the HP-UX application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the HP-UX application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the HP-UX application in the last APM polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the HP-UX application, which corresponds to the physical memory bar.

· Swap—Swap memory of the HP-UX application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory that is being used. Click the History Record icon to view the history graph of the physical or swap memory that is being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the HP-UX host by sending up to three ICMP packets. If APM receives a response packet, the ping succeeds and APM records the response time. If APM does not receive a response after sending out three ICMP packets, APM considers that the ping test has failed.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the HP-UX application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that are sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

System Load

APM analyzes and displays the system load average for the monitored HP-UX application in 1 minute, 5 minutes, and 15 minutes. System load average is the average number of processes running on the HP-UX system during a specific time period. Excessive system load can cause performance problems. The thresholds of system load vary by CPU type.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the average system load in 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the average system load in 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the average system load in 15 minutes.

File System Usage Ratio

The HP-UX file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. The HP-UX application writes data to or reads data from the physical disk partition or logical volume by using the corresponding directory.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the HP-UX directory structure.

· File System Usage Ratio—Space usage ratio of the HP-UX file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system partition or logical volume. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the change trend of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval.

· ID—ID of the zombie process in the last polling interval.

· Parent ID—ID of the parent process for the zombie process in the last polling interval.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory Usage—Memory usage of the zombie process in the last polling interval. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by HP-UX over the last 1 hour.

· Today's Traffic—Total traffic sent and received by HP-UX since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of the network interface card in HP-UX. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of the network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of HP-UX network interface cards.

· Send Rate—Send rate of a network interface card in the last polling interval.

Error Log

APM examines the HP-UX error logs during polling and displays the first 10 error logs obtained in the HP-UX application monitor report. Click More to view all error logs if the monitor report has more than 10 error logs.

The Error Log area contains the following fields:

· Time—Time when the error occurred in the last polling interval.

· Log—Content of the error log.

Process

By default, the list does not contain any processes. To monitor a process on HP-UX, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select the processes to be monitored in the monitor list window.

· Process—Name of the monitored process. APM can respectively collect monitored data for the processes that have the same name but different Process Identifiers (PIDs).

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process of the process.

· CPU Usage—CPU usage ratio of the monitored process in the last polling interval.

¡ Click the Threshold setting icon to set alarm thresholds of the CPU usage ratio for the monitored process.

¡ Click the History Record icon to view the history graph of the CPU usage ratio of the monitored process.

· Memory Usage—Memory usage ratio of the monitored process in the last polling interval. Click the History Record icon to view the history graph of the memory usage ratio of the monitored process.

· CPU Time—Duration that the process occupies the CPU in the last polling interval.

I/O State

APM can monitor the I/O status of the disk drivers in the HP-UX system.

The I/O State area contains the following fields:

· Device Name—Name of the disk drivers in the HP-UX system.

· I/O Rate—Size of the input/output data in the disk driver per second in the last polling interval.

· Searches/Sec—Number of search times in the disk driver per second in the last polling interval.

Session Information

The Session Information area displays HP-UX session login information.

The Session Information area contains the following fields:

· User Name—User logging in to HP-UX in the last polling interval.

· TTY—TTY used by the user.

· Login IP—Client IP address used when the user logged in to HP-UX.

· Login Time—Time when the user logged in to HP-UX.

· Idle—Idle time after the user logged in to HP-UX.

· Command—Most recently executed command after the user logged in to HP-UX.

inode

Index nodes (inodes) are required when you create a file or directory in the HP-UX file system. If the inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system on the HP-UX server.

· Total—Total number of available inodes in the file system in the last polling interval. Click the History Record icon to view the history graph of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system in the last polling interval. Click the History Record icon to view the history graph of the number of idle inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds of the inode usage in the file system.

¡ Click the History Record icon to view the history graph of inode usage in the file system.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

AS400

AS400 is a small-sized to medium-sized multiuser commercial operating system developed by IBM. Its performance and stability determines the performance of applications running on it. APM provides the ability to monitor the AS400 V6R1M0 version.

Adding an AS400 application monitor

APM monitors AS400 applications through class libraries provided by AS400. When you add an AS400 application monitor, follow these guidelines:

· Contact the AS400 administrator to obtain the username and password of AS400. As a best practice, use an AS400 account with the QSECOFR permission. If you use an AS400 account with the USER permission, make sure the account has the following permissions:

¡ Permission to access the QMPGDATA or QPFRDATA library.

¡ ALLOBJ, SAVSYS, JOBCTL, and SPLCTL permissions.

· Add AS400 servers to the IMC platform so that APM can obtain and display network connections of the servers and their access devices in the application topology. For more information about adding servers to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To contain traffic statistics in the monitor report about an AS400 application, configure a minimum of one probe in APM. After an AS400 application monitor is added, APM sends the IP address of the monitored AS400 application to the probes for traffic collection.

To add an AS400 application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click AS400 of the UNIX Server Monitor class.

The page for adding an AS400 application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the server on which the AS400 application to be monitored is installed. APM automatically checks the specified IP address and associates the application monitor with the server managed in the IMC platform. If the server is already added to the IMC platform, you can also click Select and then select the server in the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, use the application type_host IP address name format.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Username/Password—Enter the AS400 username and password.

¡ Contact—Enter user contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of AS400 applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that AS400 depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the AS400 application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify the connectivity to the application by using the previous parameter settings. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the application connectivity.

5. Click OK.

Modifying an AS400 application monitor

Authorized users can modify all parameters except the IP address and the APM server for an AS400 application monitor. When the IP address of a monitored AS400 server changes, operators must add a new application monitor for the server. The new application monitor cannot inherit the history data from the previous application monitor.

To modify an AS400 application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click the Modify icon for the AS400 application monitor you want to modify.

The page for modifying the AS400 application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding an AS400 application monitor."

5. Click OK.

Viewing the AS400 application monitor report

After an AS400 application monitor is added, APM collects index data for the application, and calculates its availability and health status. You can obtain monitor indexes for AS400 by viewing the monitor report.

To access the AS400 application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of an AS400 application monitor to display the report.

Figure 60 shows only a small part of an AS400 monitor report.

Figure 60 Part of an AS400 application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the monitored AS400 application.

· IP Address—IP address of the AS400 server.

· Application Description—Description of the monitored application.

· Application Type—Type of the monitored application, which is always AS400.

· Relationship—Click the Relationship icon to view dependencies between the AS400 application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarms—Latest five unrecovered alarms on the AS400 server. If AS400 did not generate alarms, this field is not displayed.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the AS400 application in the most recent polling interval.

¡ Click the Weekly History icon to view the availability of the AS400 application in the most recent 7 days.

¡ Click the Monthly History icon to view the availability of the AS400 application in the most recent 30 days.

· Available Time—Total amount of time that the AS400 application was available after 00:00 today.

· Unavailable Time—Total amount of time that the AS400 application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the AS400 application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the AS400 application was in unmanaged state after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed if its value is 0.

System Status

The System Status area contains the following fields:

· Main Memory—Size of the main memory of AS400.

· Processing Unit Count—Number of AS400 processing units.

· Running Job Count—Total number of AS400 running system jobs.

· Waiting Job Count—Number of jobs that are waiting to run on AS400.

CPU Usage

The CPU Usage area contains the following field:

· CPU Usage Ratio—CPU usage of the AS400 application. Click the History Record icon to view the history graph of the CPU usage.

iASP

The iASP area contains the following field:

· iASP—Independent auxiliary storage pools (iASP) of the AS400 application. Click the History Record icon to view the history graph of the iASP.

System ASP

The System ASP area contains the following fields:

· System ASP Usage—Ratio of the available disk space size to the total disk space size in the system. Click the History Record icon to view the history graph of the system ASP usage.

· System ASP—Available disk space size in the system. Click the History Record icon to view the history graph of the system ASP.

Subsystem

The Subsystem area contains the following fields:

· Name—Name of the subsystem, which is specified on the Start Subsystem (STRSBS) command.

· Library—Name of the library to which the subsystem belongs.

· Current Active Jobs—Number of active jobs in the subsystem. Multiple interactive jobs started from the same work station are counted as only one job.

· Maximum Active Jobs—Maximum number of active jobs allowed in the subsystem.

· Status—Status of the subsystem. Options are:

¡ ACTIVE

¡ END (in the process of ending)

¡ RSTD (the controlling subsystem is in the restricted condition)

Message Queue

The Message Queue area contains the following fields:

· Message ID—ID of the message.

· Severity—A two-digit value in the range of 00 through 99. A higher value indicates a severer level.

· Type—Type of message. Options are:

¡ Completion—Indicates the completion of work.

¡ Diagnostic—Indicates errors in a system function, application, or input data.

¡ Informational—Provides general non-error-related information.

¡ Inquiry—Conveys information and asks for a reply.

¡ Sender Copy—Contains a copy of an Inquiry or Notify message that is kept in the sender message queue.

¡ Request—Contains a command for processing by a request processor, for example, a command entry.

¡ Request_With_Prompting—Contains a request with prompting.

¡ Notify—Indicates that a program requires a corrective action or a reply.

¡ Escape—Indicates that a program must be terminated abnormally.

¡ Reply_not_Validity_Checked—Contains a reply to an Inquiry or Notify message. The message validity is not checked.

¡ Reply_Validity_Checked—Contains a reply to an Inquiry or Notify message. The message validity is checked.

¡ Reply_Message_Default_Used—Contains a reply to an Inquiry or Notify message. The message is used by default.

¡ Reply_System_Default_Used—Contains a reply to an Inquiry or Notify message. The system is used by default.

¡ Reply_from_System_Reply_List—Contains a reply to an Inquiry or Notify message. The reply is from the system reply list.

· Date—Date when the message was sent.

· Job ID—ID of the job that generates the message.

· Message—Content of the message.

Job

The Job area contains the following fields:

· Job Name—Job name identified by AS400.

· User—The username is the same as the user profile name. The username can come from different sources, depending on the type of job.

· ID—Job number assigned by the system.

· Type—Type of active job. Options are:

¡ ASJ—Autostart.

¡ BCH—Batch.

¡ BCI—Batch immediate.

¡ EVK—Started by a procedure start request.

¡ INT—Interaction.

¡ M36—Advanced 36 server job.

¡ MRT—Multiple request terminal.

¡ PJ—Prestart job.

¡ PDJ—Print drive job.

¡ RDR—Reader.

¡ SBS—Subsystem monitor.

¡ SYS—System.

¡ WTR—Writer Status.

· Status—Status of the initial thread of the job. If initial thread is in transition, this field is empty.

· I/O Operation Count—Number of I/O operations during intermission.

· Response Time—Average interaction response time of the job during intermission.

System Log

The System Log area contains the following fields:

· Message ID—ID of the message.

· Severity—A two-digit value in the range of 00 through 99. A higher value indicates a severer level.

· Type—Type of the log. Options are:

¡ 1—Completion. It indicates the completion of work.

¡ 2—Diagnostic. It indicates errors in a system function, errors in an application, or errors in input data.

¡ 4—Informational. It provides general non-error-related information.

¡ 5—Inquiry. It conveys information and asks for a reply.

¡ 6—Sender Copy. It contains a copy of an Inquiry or Notify message that is kept in the sender message queue.

¡ 8—Request. It contains a command for processing by a request processor, for example, a command entry.

¡ 10—Request_With_Prompting. Contains a request with prompting.

¡ 14—Notify. It indicates that a program requires a corrective action or a reply.

¡ 15—Escape. It indicates that a program must be terminated abnormally.

¡ 21—Reply_not_Validity_Checked. It contains a reply to an Inquiry or Notify message. The message validity is not checked.

¡ 22—Reply_Validity_Checked. It contains a reply to an Inquiry or Notify message. The message validity is checked.

¡ 23—Reply_Message_Default_Used. It contains a reply to an Inquiry or Notify message. The message is used by default.

¡ 24—Reply_System_Default_Used. It contains a reply to an Inquiry or Notify message. The system is used by default.

¡ 25—Reply_from_System_Reply_List. It contains a reply to an Inquiry or Notify message. The reply is from the system reply list.

· Message—Content of the message.

· Date—Date when the log was sent.

Hardware Resource

The Hardware Resources area contains the following fields:

· Resource Name—Name of the hardware resource.

· Resource Status—Status of the hardware resource.

· Resource Type—Type of the hardware resource.

· Resource Serial Number—Serial number of the hardware resource.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by AS400 over the last 1 hour.

· Today's Traffic—Total traffic sent and received by AS400 since 00:00 today.

Linux server monitor

This chapter describes how to add and modify monitors for Linux servers, and how to view the monitor reports.

Linux

Linux is a popular open source operating system that has multiple release versions. By monitoring Linux, operators can view how the operating performance of a Linux server affects network applications on the system.

Adding a Linux application monitor

APM monitors Linux applications through agents, SNMP, or CLI. When you add Linux application monitors, follow these guidelines:

· To monitor a Linux application through an agent, deploy the agent on the host on which the Linux operating system is installed. For more information about agents, see "APM agent management."

· To monitor a Linux application through SNMP:

¡ Enable and configure SNMP for the host on which the Linux operating system is installed. For more information about enabling SNMP on Linux, see the Linux help.

¡ Obtain the read-only and read-write community strings.

· To monitor a Linux application through CLI:

¡ Enable and configure Telnet or SSH on Linux. For more information about enabling Telnet or SSH on Linux, see the Linux configuration guide.

¡ Obtain the username and password of the Telnet or SSH user who has the Linux administrator's privileges.

· Add the Linux hosts to the IMC platform so APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the Linux application, make sure at least one probe is configured in APM. After a Linux application monitor is added, APM sends the IP address of the monitored Linux application to the probes for traffic collection.

The following task is performed in remote monitor mode. When the local monitor mode is used, you need to configure only part of the parameters that are required for the remote monitor mode.

To add a Linux application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click Linux of the Linux Server Monitor class.

The page for adding a Linux application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the Linux application to be monitored is installed. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start." APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform.

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval provides more accurate realtime data, but consumes more system resources. This field is available only when you select Disable from the Use Template list.

¡ Monitor Type—Select the protocol (SSH, SNMP, or Telnet) through which APM monitors the Linux application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SNMP is selected, configure the following parameters:

- Edit SNMP Parameters—Select this option if you want to manually configure SNMP parameters for APM. Make sure the SNMP settings are the same as those on Linux.

- Parameter Type—Select the SNMP parameter type. Options are SNMPv1, SNMPv2c, and SNMPv3 Template. The SNMPv3 Template option is available only when Select an Existing Template is selected.

- Read-Only Community String—Enter the SNMP read-only community string, with which APM can read MIB variables from the Linux host.

- Read-Write Community String—Enter the read-write SNMP community string, with which APM can read MIB variables from or write MIB variables to the Linux host.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for an SNMP response from Linux. The value range is 1 to 60 seconds and the default is 4 seconds. If no SNMP response is received from Linux within the timeout time, APM considers that the interaction has failed.

- Retries (1-20)—Enter how many times APM retries to send SNMP packets to the Linux host.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on Linux.

- Username—Enter the SSH username. The user must have the Linux administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on Linux.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from Linux. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from Linux within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the Linux host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on Linux.

- Username—Enter the Telnet username. The user must have the Linux administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from Linux. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from Linux within the timeout time, APM considers that the interaction has failed.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of Linux applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that Linux depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the Linux application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the connection.

5. Click OK.

Modifying a Linux application monitor

Authorized users can modify all parameters except the IP address and the APM server for a Linux application monitor. When the IP address of a monitored Linux host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a Linux application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The page displays all application types that can be monitored by APM.

3. Click the Modify icon for the Linux application monitor you want to modify.

The page for modifying the Linux application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a Linux application monitor."

5. Click OK.

Viewing the Linux application monitor report

After adding the Linux application monitor, APM collects application index data to calculate its availability and health status. You can obtain monitor indexes for Linux by viewing the monitor report.

To access the Linux application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a Linux application monitor to display the report.

Figure 61 shows part of a Linux application monitor report.

Figure 61 Part of a Linux application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the Linux application.

· IP Address—IP address of the Linux host.

· Application Type—Type of the monitored application, which is always Linux.

· Version—Version of the Linux operating system.

· Last Polling Time—Time when APM last polled the Linux application.

· System Running Time—Duration since the startup of the Linux application to the time when APM last polled the Linux application.

· Relationship—Click the Related Applications icon to view dependencies between the Linux application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarm—Latest five unrecovered alarms on the Linux host. This field is not displayed if no alarm is generated by the Linux application.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the Linux application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the Linux application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the Linux application in the last 30 days.

· Available Time—Total amount of time that the Linux application was available after 00:00 today.

· Unavailable Time—Total amount of time that the Linux application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the Linux application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the Linux application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed when its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the Linux application in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ History Record—Click the History Record icon to view the history graph of the CPU usage ratio.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the Linux application, which corresponds to the physical memory bar.

· Swap—Swap memory of the Linux application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory being used. Click the History Record icon to view the history graph of the physical or swap memory being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

CPU Performance

The CPU Performance area contains the following fields:

· CPU Name—Name of the CPU.

· Nice CPU—Time taken by the processes whose priorities were modified by using the Nice command.

· Load Percentage—Percentage of the load time.

· User Percentage—Percentage of the user time.

· System Percentage—Percentage of the system time.

· I/O Wait Percentage—Percentage of the I/O wait time.

· Idle Percentage—Percentage of the idle time.

You can click the History Record icon to view the history graph of a monitor index.

Paging

The Paging area contains the following fields:

· Paging In—Number of pages that were paged in.

· Paging Out—Number of pages that were paged out.

· Paging Total—Total number of pages that were paged in and out.

· Paging In Rate—Number of pages that were paged in per second.

· Paging Out Rate—Number of pages that were paged out per second.

· Paging Rate—Number of pages that were paged in and out per second.

You can click the History Record icon to view the history graph of a monitor index.

Ping Test

When the polling interval expires, APM pings the Linux host by sending up to three ICMP packets. When APM receives a response, it considers the ping test a success and records the response time. When APM receives no response after three tries, it considers the ping test a failure.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the Linux application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that are sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

System Load

APM counts the average system load over 1 minute, 5 minutes, and 15 minutes. The average system load records the average number of processes in the run queue over a specific time interval. An overloaded system results in severe performance issues. The load threshold value varies by CPU model.

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the system load over the last 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the system load over the last 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the system load over the last 15 minutes.

File System Usage Ratio

The Linux file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. Use the File System Usage Ratio area to display how the available disk space is used.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the Linux directory structure.

· File System Usage Ratio—Space usage ratio of the Linux file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system. Click the History Record icon to view the history graph of the free file system space.

I/O Response

The I/O Response area contains the following fields:

· Disk Name—Name of a Linux server disk.

· Response—Average time (in milliseconds) for I/O requests issued to the disk.

· Average Queue—Average queue length of the requests that were issued to the disk.

· Transfer Time—Percentage of CPU time during which I/O requests were issued to the disk.

Adapter

The Adapter area contains the following fields:

· Adapter Name—Name of the adapter installed on the Linux server.

· Adapter Status—Status of the adapter, UP or DOWN.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes in the last polling interval. Click the History Record icon to view the history graph of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process in the last polling interval.

· ID—ID of the zombie process in the last polling interval.

· Parent ID—ID of the parent process for the zombie process in the last polling interval.

· CPU Usage—CPU usage of the zombie process in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory usage—Memory usage of the zombie process in the last polling interval. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU in the last polling interval.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by the Linux application over the last 1 hour.

· Today's Traffic—Total traffic sent and received by the Linux application since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of a network interface card in Linux. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of a network interface card in the last polling interval. Click the Set Threshold icon to set alarm thresholds for the receive rate of Linux network interface cards

· Send Rate—Send rate of a network interface card in the last polling interval.

· Input Error Packet Rate—Number of inbound erroneous packets per second on a network interface card in the last polling interval.

· Output Error Packet Rate—Number of outbound erroneous packets per second on a network interface card in the last polling interval.

Error Log

APM examines the Linux error logs during polling and displays the first 10 error logs obtained in the polling in the Linux application monitor report. Click More to view all error logs in the last polling interval if the report has more than 10 error logs.

The Error Log area contains the following fields:

· Time—Time when the error occurred.

· Log—Content of the error log.

TCP Connections

The TCP Connections area contains the following fields:

· Active Connections Rate—Number of active connections per second.

· Passive Connections Rate—Number of passive connections per second.

· Failed Connections Rate—Number of failed connections per second.

· Reset Connections Rate—Number of reset connections per second.

· Established Connections—Number of established connections.

· Received Segments Rate—Number of received segments per second.

· Sent Segments Rate—Number of sent segments per second.

· Retransmitted Segments Rate—Number of retransmitted segments per second.

Process Number

The Process Number area contains the following field:

Process Number—Number of processes on the Linux server.

I/O State

APM can monitor the I/O status of disks, partitions, or logical volumes in Linux.

The I/O State area contains the following fields:

· Device Name—Name of the disk, partition, or logical volume in Linux.

· I/O Read Rate—Data output rate of the disk, partition, or logical volume in Linux.

· I/O Write Rate—Data input rate of the disk, partition, or logical volume in Linux.

Process

By default, the list does not contain any processes. To monitor processes on Linux, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select processes to be monitored in the monitor list window.

· Process Name—Name of the monitored process. For processes with the same name but different Process Identifiers (PIDs), APM collects the CPU usage ratio and the memory usage ratio for each process. For example, the application may generate a lot of httpd processes, and APM collects the CPU usage ratio and the memory usage ratio for each httpd process selected.

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process for the process.

· CPU Usage—CPU usage ratio of the process.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

· Memory Usage—Memory usage ratio of the process. Click the History Record icon to view the history graph of the memory usage.

· CPU Time—Duration that the process occupies the CPU.

· Arguments—Arguments of a process on the Linux server.

inode

The inodes are required when you create a file or directory in the Linux file system. If inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system on the Linux server.

· Total—Total number of available inodes in the file system. Click the History Record icon to view the change trend of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system. Click the History Record icon to view the change trend of the number of idle inodes in the file system.

· In Use—Number of inodes that have been used in the file system. Click the History Record icon to view the change trend of the number of used inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system inode usage.

¡ Click the History Record icon to view the history graph of inode usage in the file system.

Vol Group

Logical volume management manages disk partitions in the Linux operating system. It combines one or more physical disks to a volume group and creates a logical volume for the volume group. One logical volume equals a disk partition.

The Vol Group area contains the following fields:

· Name—Name of the volume group.

· Size—Size of the volume group. Click the History Record icon to view the history graph of the volume group size.

· In Use—Volume group space that is used in the last polling interval. Click the History Record icon to view the change trend of the used volume group space.

· Free Space—Volume group space that are not used in the last polling interval. Click the History Record icon to view the history graph of the volume group space.

· Usage Ratio—Usage of the volume group space in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the space usage of the volume group.

¡ Click the History Record icon to view the history graph of the space usage of the volume group.

Session Information

The Session Information area displays Linux session login information.

The Session Information area contains the following fields:

· User Name—User logging in to Linux in the last polling interval.

· TTY—TTY used by the user.

· Login IP—Client IP address used when the user logs in to Linux. The value of :0 indicates that the user logs in to Linux through the console.

· Login Time—Time when the user logged in to Linux.

· Idle—Idle time after the user logged in to Linux.

· Command—Most recently executed command after the user logged in to Linux.

Memory Info

The Memory Info area contains the following fields:

· Locator—Position of the memory card on the server.

· Memory Size—Size of the memory.

CPU Info

The CPU Info area contains the following fields:

· Locator—Position of the CPU on the server.

· Cores—Number of CPU cores.

· Logic Processors—Number of CPU logic processors.

· CPU Model—Model of the CPU.

Base Board

The Base Board area contains the following fields:

· Manufacturer—Manufacturer of the base board.

· Product Name—Model of the base board.

· Serial Number—Serial number of base board.

Chassis

The Chassis area contains the following fields:

· Manufacturer—Manufacturer of the chassis.

· Power Supply State—State of the chassis power supply.

· Serial Number—Serial number of the chassis.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

NeoKylin

NeoKylin is an operating system that uses Linux kernels. By monitoring NeoKylin, operators can view how the operating performance of a NeoKylin server affects network applications on the system. APM supports monitoring NeoKylin V6.0.

Adding a NeoKylin application monitor

APM monitors NeoKylin applications through SNMP, CLI, or agents. When you add NeoKylin application monitors, follow these guidelines:

· To monitor a NeoKylin application through an agent, deploy the agent on the host where the NeoKylin operating system is installed. For more information about agents, see "APM agent management."

· To monitor a NeoKylin application through SNMP:

¡ Enable and configure SNMP for the host on which the NeoKylin operating system is installed. For more information about enabling SNMP on NeoKylin, see the NeoKylin online help.

¡ Obtain the read-only and read-write community strings.

· To monitor a NeoKylin application through CLI:

¡ Enable and configure Telnet or SSH on NeoKylin. For more information about enabling Telnet or SSH on NeoKylin, see the NeoKylin configuration guide.

¡ Obtain the username and password of the Telnet or SSH user who has the NeoKylin administrator's privileges.

· Add the NeoKylin hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the NeoKylin application, make sure at least one probe is configured in APM. After a NeoKylin application monitor is added, APM sends the IP address of the monitored NeoKylin application to the probes for traffic collection.

To add a NeoKylin application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click NeoKylin of the Linux Server Monitor class.

The page for adding a NeoKylin application monitor opens.

Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the NeoKylin application to be monitored is installed. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start." APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform.

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval provides more accurate realtime data, but consumes more system resources. This field is available only when you select Disable from the Use Template list.

¡ Monitor Type—Select the protocol (SSH, SNMP, or Telnet) through which APM monitors the NeoKylin application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SNMP is selected, configure the following parameters:

- Edit SNMP Parameters—Select this option if you want to manually configure SNMP parameters for APM. Make sure the SNMP settings are the same as those on NeoKylin.

- Parameter Type—Select the SNMP parameter type. Options are SNMPv1, SNMPv2c, and SNMPv3 Template. The SNMPv3 Template option is available only when Select an Existing Template is selected.

- Read-Only Community String—Enter the SNMP read-only community string, with which APM can read MIB variables from the NeoKylin host.

- Read-Write Community String—Enter the read-write SNMP community string, with which APM can read MIB variables from or write MIB variables to the NeoKylin host.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for an SNMP response from NeoKylin. The value range is 1 to 60 seconds and the default is 4 seconds. If no SNMP response is received from NeoKylin within the timeout time, APM considers that the interaction has failed.

- Retries (1-20)—Enter how many times APM retries to send SNMP packets to the NeoKylin host.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on NeoKylin.

- Username—Enter the SSH username. The user must have the NeoKylin administrator's privilege.

- Password—Enter the password of the SSH user.

- Private Key File—Enter the directory of the SSH private key file or browse to the file.

- Private Key Password—Enter the password to decrypt the SSH private key file.

- Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on NeoKylin.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from NeoKylin. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from NeoKylin within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the NeoKylin host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on NeoKylin.

- Username—Enter the Telnet username. The user must have the NeoKylin administrator's privilege.

- Password—Enter the password of the Telnet user.

- Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from NeoKylin. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from NeoKylin within the timeout time, APM considers that the interaction has failed.

¡ Use IPMI—Select Enable or Disable from the list. If you select Enable, configure the following parameters:

- Host IP—Enter the IP address of the BMC for IPMI monitoring.

- Username/Password—Enter the username and password of the BMC for IPMI monitoring.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of NeoKylin applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that NeoKylin depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the NeoKylin application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the connection.

4. Click OK.

Modifying a NeoKylin application monitor

Authorized users can modify all parameters except the IP address and the APM server for a NeoKylin application monitor. When the IP address of a monitored NeoKylin host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a NeoKylin application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The page displays all application types that can be monitored by APM.

3. Click the Modify icon for the NeoKylin application monitor you want to modify.

The page for modifying the NeoKylin application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a NeoKylin application monitor."

5. Click OK.

Viewing the NeoKylin application monitor report

After a NeoKylin application monitor is added, APM collects application index data, evaluates the availability and health status, and updates the monitor report. The report shows the index values obtained from the most recent polling of the application.

To access the NeoKylin application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a NeoKylin application monitor to display the report.

Figure 62 shows part of a NeoKylin application monitor report.

Figure 62 Part of a NeoKylin application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the NeoKylin application.

· IP Address—IP address of the NeoKylin host.

· Application Type—Type of the monitored application, which is always NeoKylin.

· Version—Version of the NeoKylin operating system.

· System Running Time—Duration since the startup of the NeoKylin application to the time when APM last polled the NeoKylin application.

· Last Polling Time—Time when APM last polled the NeoKylin application.

· Relationship—Click the Related Applications icon to view dependencies between the NeoKylin application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarm—Latest five unrecovered alarms on the NeoKylin host. This field is not displayed if no alarm is generated by the NeoKylin application.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the NeoKylin application.

¡ Click the Weekly History icon to view the availability of the NeoKylin application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the NeoKylin application in the last 30 days.

· Available Time—Total amount of time that the NeoKylin application was available after 00:00 today.

· Unavailable Time—Total amount of time that the NeoKylin application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the NeoKylin application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the NeoKylin application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed when its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the NeoKylin application.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage ratio.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the NeoKylin application, which corresponds to the physical memory bar.

· Swap—Swap memory of the NeoKylin application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory being used. Click the History Record icon to view the history graph of the physical or swap memory being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the NeoKylin host by sending up to three ICMP packets. When APM receives a response, it considers the ping test a success and records the response time. When APM receives no response after three tries, it considers the ping test a failure.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the NeoKylin application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that are sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

System Load

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the system load over the last 1 minute.

· System Load/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the system load over the last 5 minutes.

· System Load/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the system load over the last 15 minutes.

File System Usage Ratio

The NeoKylin file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or logical volume. Use the File System Usage Ratio area to display how the available disk space is used.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the NeoKylin directory structure.

· File System Usage Ratio—Space usage ratio of the NeoKylin file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes. Click the History Record icon to view the history graph of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process.

· ID—ID of the zombie process.

· Parent ID—ID of the parent process for the zombie process.

· CPU Usage—CPU usage of the zombie process.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory usage—Memory usage of the zombie process. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by the NeoKylin application over the last 1 hour.

· Today's Traffic—Total traffic sent and received by the NeoKylin application since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of a network interface card in NeoKylin. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of a network interface card. Click the Set Threshold icon to set alarm thresholds for the receive rate of NeoKylin network interface cards

· Send Rate—Send rate of a network interface card.

· Input Error Packet Rate—Number of inbound erroneous packets per second on a network interface card.

· Output Error Packet Rate—Number of outbound erroneous packets per second on a network interface card.

Error Log

APM examines the NeoKylin error logs during polling and displays the first 10 error logs obtained in the polling in the NeoKylin application monitor report. Click More to view all error logs in the last polling interval if the report has more than 10 error logs.

The Error Log area contains the following fields:

· Time—Time when the error occurred.

· Log—Content of the error log.

Process

By default, the list does not contain any processes. To monitor processes on NeoKylin, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select processes to be monitored in the monitor list window.

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process for the process.

· CPU Usage—CPU usage ratio of the process.

¡ Click the Set Threshold icon to set alarm thresholds for the NeoKylin process CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

· Memory Usage—Memory usage ratio of the process. Click the History Record icon to view the history graph of the memory usage.

· CPU Time—Duration that the process occupies the CPU.

I/O State

APM can monitor the I/O status of disks, partitions, or logical volumes in NeoKylin.

The I/O State area contains the following fields:

· Device Name—Name of the disk, partition, or logical volume in NeoKylin.

· I/O Read Rate—Data output rate of the disk, partition, or logical volume in NeoKylin.

· I/O Write Rate—Data input rate of the disk, partition, or logical volume in NeoKylin.

inode

Index nodes (inodes) are required when you create a file or directory in the NeoKylin file system. If the inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system of the NeoKylin system.

· Total—Total number of available inodes in the file system. Click the History Record icon to view the change trend of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system. Click the History Record icon to view the change trend of the number of idle inodes in the file system.

· In Use—Number of inodes that have been used in the file system. Click the History Record icon to view the change trend of the number of used inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system inode usage.

¡ Click the History Record icon to view the history graph of inode usage in the file system.

Vol Group

Logical volume management manages disk partitions in the NeoKylin operating system. It combines one or more physical disks to a volume group and creates a logical volume for the volume group. One logical volume equals a disk partition.

The Vol Group area contains the following fields:

· Name—Name of the volume group.

· Size—Size of the volume group. Click the History Record icon to view the history graph of the volume group size.

· In Use—Volume group space that is used. Click the History Record icon to view the change trend of the used volume group space.

· Free Space—Volume group space that are not used. Click the History Record icon to view the history graph of the volume group space.

· Usage Ratio—Usage of the volume group space.

¡ Click the Set Threshold icon to set alarm thresholds for the space usage of the volume group.

¡ Click the History Record icon to view the history graph of the space usage of the volume group.

Session Information

The Session Information area displays NeoKylin session login information and contains the following fields:

· User Name—User logging in to NeoKylin.

· TTY—TTY used by the user.

· Login IP—Client IP address used when the user logs in to NeoKylin. The value of :0 indicates that the user logs in to NeoKylin through the console.

· Login Time—Time when the user logged in to NeoKylin.

· Idle—Idle time after the user logged in to NeoKylin.

· Command—Most recently executed command after the user logged in to NeoKylin.

Memory

The Memory area displays memory information for the server where the OS is located. To monitor the memory, make sure the BMC is installed on the server.

The Memory area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Power Supply

The Power Supply area displays power supply information for the server where the OS is located. To monitor the power supply, make sure the BMC is installed on the server.

The Power Supply area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Temperature

The Temperature area displays temperature information for the server where the OS is located. To monitor the temperature, make sure the BMC is installed on the server.

The Temperature area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

· Value—Temperature of the component.

Fan

The Fan area displays fan information for the server where the OS is located. To monitor the fans, make sure the BMC is installed on the server.

The Fan area contains the following fields:

· Component Name—Name of the component.

· Status—State of the component.

Board

The Board area displays board information about the server where the OS is located. To monitor the board, make sure the BMC is installed on the server.

The Board area contains the following fields:

· Manufacturer—Manufacturer of the board.

· Product Name—Name and model of the product to which the board applies.

· Production Date—Production date of the board.

· Part Number—Part number of the board.

· Serial Number—Serial number of the board.

· System GUID—GUID of the board.

Chassis

The Chassis area displays chassis information for the server where the OS is located. To monitor the chassis, make sure the BMC is installed on the server.

The Chassis area contains the following fields:

· BMC Version—Version of the BMC.

· IPMI Driver Type—Type of the IPMI driver.

· Self-Check Result—Self-check result of the server.

· Power Supply Status—State of the power supply for the chassis.

· Chassis Intrusion—Whether the chassis is open or has been opened before.

· Front Panel—Whether the front panel is open.

· Cooling Fan Fault—Whether the cooling fans operate correctly.

· Disk Fault—Whether the disks operate correctly.

· Power-On Hours—Hours since the chassis was started.

Rocky

Rocky is an operating system that uses Linux kernels. By monitoring Rocky, operators can view how the operating performance of a Rocky server affects network applications on the system.

Adding a Rocky application monitor

APM monitors Rocky applications through SNMP, CLI, or agents. When you add Rocky application monitors, follow these guidelines:

· To monitor a Rocky application through an agent, deploy the agent on the host where the Rocky operating system is installed. For more information about agents, see "APM agent management."

· To monitor a Rocky application through SNMP:

¡ Enable and configure SNMP for the host on which the Rocky operating system is installed. For more information about enabling SNMP on Rocky, see the Rocky administrator guide.

¡ Obtain the read-only and read-write community strings.

· To monitor a Rocky application through CLI:

¡ Enable and configure Telnet or SSH on Rocky. For more information about enabling Telnet or SSH on Rocky, see the Rocky administrator guide.

¡ Obtain the username and password of the Telnet or SSH user who has the Rocky administrator's privileges.

· Add the Rocky hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the Rocky application, make sure at least one probe is configured in APM. After a Rocky application monitor is added, APM sends the IP address of the monitored Rocky application to the probes for traffic collection.

To add a Rocky application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Manager > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click Rocky of the Linux Server Monitor class.

The page for adding a Rocky application monitor opens.

Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the Rocky application to be monitored is installed. If the host is already added to the IMC platform, you can also click Select, and then select the host in the Select Devices window. For information about selecting a host, see "Quick start." APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform.

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval provides more accurate realtime data, but consumes more system resources. This field is available only when you select Disable from the Use Template list.

¡ Monitor Type—Select the protocol (SSH, SNMP, or Telnet) through which APM monitors the Rocky application, and then click the Configure icon to configure related parameters. This field is available only when you select Disable from the Use Template list.

When SNMP is selected, configure the following parameters:

- Edit SNMP Parameters—Select this option if you want to manually configure SNMP parameters for APM. Make sure the SNMP settings are the same as those on Rocky.

- Parameter Type—Select the SNMP parameter type. Options are SNMPv1, SNMPv2c, and SNMPv3 Template. The SNMPv3 Template option is available only when Select an Existing Template is selected.

- Read-Only Community String—Enter the SNMP read-only community string, with which APM can read MIB variables from the Rocky host.

- Read-Write Community String—Enter the read-write SNMP community string, with which APM can read MIB variables from, or write MIB variables to, the Rocky host.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for an SNMP response from Rocky. The value range is 1 to 60 seconds and the default is 4 seconds. If no SNMP response is received from Rocky within the timeout time, APM considers that the interaction has failed.

- Retries (1-20)—Enter how many times APM retries to send SNMP packets to the Rocky host.

When SSH is selected, configure the following parameters:

- Edit SSH Parameters—Select this option if you want to manually configure SSH parameters for APM. Make sure the SSH settings are the same as those on Rocky.

The following parameters to be configured vary with authentication modes:

Username—Enter the SSH username. The user must have the Rocky administrator's privilege.

Password—Enter the password of the SSH user.

Private Key File—Enter the directory of the SSH private key file or browse to the file.

Private Key Password—Enter the password to decrypt the SSH private key file.

Super Password—Enter the super password with which an SSH user can elevate privileges after login.

- Port—Enter the SSH port on Rocky.

- Timeout (1-120 seconds)—Enter the maximum time period that APM waits for an SSH response from Rocky. The value range is 1 to 120 seconds and the default is 10 seconds. If no SSH response is received from Rocky within the timeout time, APM considers that the interaction has failed.

- Retries (1-5)—Enter how many times APM retries to send SSH packets to the Rocky host.

When Telnet is selected, configure the following parameters:

- Edit Telnet Parameters—Select this option if you want to manually configure Telnet parameters for APM. Make sure the Telnet settings are the same as those on Rocky.

The following parameters to be configured vary with authentication modes:

Username—Enter the Telnet username. The user must have the Rocky administrator's privilege.

Password—Enter the password of the Telnet user.

Super Password—Enter the super password with which a Telnet user can elevate privileges after login.

- Timeout (1-60 seconds)—Enter the maximum time period that APM waits for a Telnet response from Rocky. The value range is 1 to 60 seconds and the default is 4 seconds. If no Telnet response is received from Rocky within the timeout time, APM considers that the interaction has failed.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of Rocky applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that Rocky depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology.

¡ Application Group—Specify an application group for the Rocky application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the connection.

4. Click OK.

Modifying a Rocky application monitor

Authorized users can modify all parameters except the IP address and the APM server for a Rocky application monitor. When the IP address of a monitored Rocky host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a Rocky application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The page displays all application types that can be monitored by APM.

3. Click the Modify icon for the Rocky application monitor you want to modify.

The page for modifying the Rocky application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a Rocky application monitor."

5. Click OK.

Viewing the Rocky application monitor report

After a Rocky application monitor is added, APM collects application index data, evaluates the availability and health status, and updates the monitor report. The report shows the index values obtained from the most recent polling of the application.

To access the Rocky application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a Rocky application monitor to display the report.

Figure 63 shows part of a Rocky application monitor report.

Figure 63 Part of a Rocky application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the Rocky application.

· IP Address—IP address of the Rocky host.

· Application Type—Type of the monitored application, which is always Rocky.

· Version—Version of the Rocky operating system.

· System Running Time—Duration since the startup of the Rocky application to the time when APM last polled the Rocky application.

· Last Polling Time—Time when APM last polled the Rocky application.

· Relationship—Click the Related Applications icon to view dependencies between the Rocky application and other applications in a dependency topology view. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarm—Latest five unrecovered alarms on the Rocky host. This field is not displayed if no alarm is generated by the Rocky application.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the Rocky application.

¡ Click the Weekly History icon to view the availability of the Rocky application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the Rocky application in the last 30 days.

· Available Time—Total amount of time that the Rocky application was available after 00:00 today.

· Unavailable Time—Total amount of time that the Rocky application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the Rocky application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the Rocky application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed when its value is 0.

CPU Usage Ratio

The CPU Usage Ratio area contains the following field:

· CPU Usage Ratio—CPU usage ratio of the Rocky application.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage ratio.

¡ Click the History Record icon to view the history graph of the CPU usage ratio.

Memory Usage Ratio

The Memory Usage Ratio area displays information about physical memory and swap memory.

The Memory Usage Ratio area contains the following fields:

· Physical Memory—Physical memory of the Rocky application, which corresponds to the physical memory bar.

· Swap—Swap memory of the Rocky application, which corresponds to a disk space.

· Total—Total amount of the physical or swap memory.

· In Use—Size of the physical or swap memory being used. Click the History Record icon to view the history graph of the physical or swap memory being used.

· Usage Ratio—Physical or swap memory usage ratio. The usage ratio is calculated by using the following formula: Usage ratio = Memory in use/Total memory x 100%.

¡ Click the Set Threshold icon to set alarm thresholds for the physical or swap memory.

¡ Click the History Record icon to view the history graph of the physical or swap memory usage.

Ping Test

When the polling interval expires, APM pings the Rocky host by sending up to three ICMP packets. If APM receives a response, it considers the ping test a success and records the response time. If APM receives no response after three tries, it considers the ping test a failure.

The Ping Test area contains the following fields:

· Response Time—Round trip response time of the Rocky application in the last ping operation. Click the History Record icon to view the history graph of the response time.

· Packets Sent—Number of ICMP packets that are sent in the last ping operation. The maximum value is 3. Click the History Record icon to view the history graph of the sent packets.

System Load

The System Load area contains the following fields:

· System Load/Min—Average system load over the last 1 minute. Click the History Record icon to view the history graph of the system load over the last 1 minute.

· System Loads/5 Min—Average system load over the last 5 minutes. Click the History Record icon to view the history graph of the system load over the last 5 minutes.

· System Loads/15 Min—Average system load over the last 15 minutes. Click the History Record icon to view the history graph of the system load over the last 15 minutes.

File System Usage Ratio

The Rocky file directory structure contains one root directory and multiple subdirectories. File systems are mounted to the root directory or subdirectories under the root directory. Each file system corresponds to a physical disk partition or a logical volume. Use the File System Usage Ratio area to display how the available disk space is used.

The File System Usage Ratio area contains the following fields:

· Name—Mount point of the file system in the Rocky directory structure.

· File System Usage Ratio—Space usage ratio of the Rocky file system.

¡ Click the Set Threshold icon to set alarm thresholds for the file system usage.

¡ Click the History Record icon to view the history graph of the file system usage ratio.

· In Use—Used space of the file system. Click the History Record icon to view the history graph of the used file system space.

· Free Space—Free space of the file system. Click the History Record icon to view the history graph of the free file system space.

Zombie Process Number

The Zombie Process Number area contains the following field:

· Zombie Process Number—Number of zombie processes. Click the History Record icon to view the history graph of the zombie process number.

Zombie Process

The Zombie Process area contains the following fields:

· Process Name—Name of the zombie process.

· ID—ID of the zombie process.

· Parent ID—ID of the parent process for the zombie process.

· CPU Usage—CPU usage of the zombie process.

¡ Click the Set Threshold icon to set alarm thresholds for the CPU usage of the zombie process.

¡ Click the History Record icon to view the history graph of the CPU usage of the zombie process.

· Memory usage—Memory usage of the zombie process. Click the History Record icon to view the history graph of the memory usage of the zombie process.

· CPU Time—Duration that the zombie process occupies the CPU.

Application Traffic

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by the Rocky application over the last 1 hour.

· Today's Traffic—Total traffic sent and received by the Rocky application since 00:00 today.

Network Interface

The Network Interface area contains the following fields:

· Interface Name—Identifier of a network interface card in Rocky. APM monitors both physical and virtual (logical) network interface cards.

· Receive Rate—Receive rate of a network interface card. Click the Set Threshold icon to set alarm thresholds for the receive rate of Rocky network interface cards

· Send Rate—Send rate of a network interface card.

· Input Error Packet Rate—Number of inbound erroneous packets per second on a network interface card.

· Output Error Packet Rate—Number of outbound erroneous packets per second on a network interface card.

Error Log

APM examines the Rocky error log messages during polling and displays the first 10 error log messages obtained in the polling in the Rocky application monitor report. Click More to view all error log messages in the last polling interval if the report has more than 10 error logs.

The Error Log area contains the following fields:

· Time—Time when the error occurred.

· Log—Content of the error log message.

Process

By default, the list does not contain any processes. To monitor processes on Rocky, click the Configuration icon to select the processes to be monitored. APM collects the index data for the monitored processes when APM polls applications next time, including the CPU usage ratio and memory usage ratio.

The Process area contains the following fields:

· Config—Click the Config icon to select processes to be monitored in the monitor list window.

· Process Name—Name of the monitored process. For processes with the same name but different process identifiers (PIDs), APM collects the CPU usage ratio and the memory usage ratio for each process. For example, the application may generate a lot of httpd processes, and APM collects the CPU usage ratio and the memory usage ratio for each httpd process selected.

· ID—Unique identifier of the process on the OS.

· Parent ID—ID of the parent process for the process.

· CPU Usage—CPU usage ratio of the process.

¡ Click the Set Threshold icon to set alarm thresholds for the Rocky process CPU usage.

¡ Click the History Record icon to view the history graph of the CPU usage.

· Memory Usage—Memory usage ratio of the process. Click the History Record icon to view the history graph of the memory usage.

· CPU Time—Duration that the process occupies the CPU.

I/O State

APM can monitor the I/O status of disks, partitions, and logical volumes in Rocky.

The I/O State area contains the following fields:

· Device Name—Name of the disk, partition, or logical volume in Rocky.

· I/O Read Rate—Data output rate of the disk, partition, or logical volume in Rocky.

· I/O Write Rate—Data input rate of the disk, partition, or logical volume in Rocky.

inode

Index nodes (inodes) are required when you create files or directories in the Rocky file system. If the inodes are used up, you cannot create a file or directory in the file system.

The inode area contains the following fields:

· File System—File system of the Rocky system.

· Total—Total number of available inodes in the file system. Click the History Record icon to view the change trend of the total number of inodes in the file system.

· Free—Number of inodes that are not used in the file system. Click the History Record icon to view the change trend of the number of idle inodes in the file system.

· In Use—Number of inodes that have been used in the file system. Click the History Record icon to view the change trend of the number of used inodes in the file system.

· inode Usage Ratio—Usage of inodes in the file system.

¡ Click the Set Threshold icon to set alarm thresholds the inode usage.

¡ Click the History Record icon to view the history graph of inode usage.

Vol Group

Logical volume management manages disk partitions in the Rocky operating system. It combines one or more physical disks to form a volume group, and allows you to create logical volumes on the volume group. One logical volume equals a disk partition.

The Vol Group area contains the following fields:

· Name—Name of the volume group.

· Size—Size of the volume group. Click the History Record icon to view the history graph of the volume group size.

· In Use—Volume group space that is used. Click the History Record icon to view the change trend of the used volume group space.

· Free Space—Volume group space that is not used. Click the History Record icon to view the history graph of the volume group space that is not used.

· Usage Ratio—Usage of the volume group space.

¡ Click the Set Threshold icon to set alarm thresholds of the space usage of the volume group.

¡ Click the History Record icon to view the history graph of the space usage of the volume group.

Session Information

The Session Information area displays Rocky session login information and contains the following fields:

· User Name—User logged in to Rocky.

· TTY—TTY line used by the user.

· Login IP—Client IP address used by the user at login. The value of :0 indicates that the user logged in to Rocky through the console.

· Login Time—Time when the user logged in to Rocky.

· Idle—Idle time after the user logged in to Rocky.

· Command—Most recently executed command after the user logged in to Rocky.

Database server monitor

This chapter describes how to add and modify monitors for database servers, and how to view the monitor reports.

SQL Server

SQL Server is a Database Management System (DBMS) developed by Microsoft. The database performance and stability affects the operation of service applications. APM supports monitoring SQL Server applications.

Adding a SQL Server application monitor

APM can locally or remotely monitor SQL Server applications through JDBC. When you add SQL Server application monitors, follow these guidelines:

· To locally monitor SQL Server applications, install agents on the hosts where SQL Server applications are deployed. For more information about installing agents, see "APM agent management."

· Obtain the username and password of the user who has the SQL Server administrator's privileges and the authentication type.

· Obtain the instance names for SQL Server applications if the default instance name is not used.

· Add SQL Server hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the SQL Server application, make sure at least one probe is configured in APM. After a SQL Server application monitor is added, APM sends the IP address and service port of the monitored SQL Server application to the probes for traffic collection.

To add a SQL Server application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Management > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click SQL Server of the Database Server Monitor class.

The page for adding a SQL Server application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the SQL Server application to be monitored is installed. APM automatically checks the IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host from the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Application Monitor Port—Enter the service port number for the SQL Server application, 1433 by default. This field is available only when you select Disable from the Use Template list.

¡ Traffic Collection Port—Enter the service port number for the SQL Server application. This field is displayed only when at least one probe is configured for APM and when you select Enable from the Use Template list.

¡ Authentication Type—Select an authentication type for the SQL Server application. Options are Windows authentication and SQL Server authentication. This field is available only when you select Disable from the Use Template list.

¡ Username—Enter the username of the SQL Server administrator. This field is available only when you select Disable from the Use Template list.

¡ Password—Enter the password of the SQL Server administrator. This field is available only when you select Disable from the Use Template list.

¡ Instance Name—Enter the SQL Server instance name that is the same as the name configured when the SQL Server was installed. Keep this field empty if the default instance name is used. This field is available only when you select Disable from the Use Template list.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of SQL Server applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that SQL Server depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology. APM automatically adds the dependencies between SQL Server and operating system applications by IP address and displays their dependencies in the application topology.

¡ Application Group—Specify an application group for the SQL Server application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connection to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not selected, APM adds the application monitor without verifying the connection.

5. Click OK.

Modifying a SQL Server application monitor

Authorized users can modify all parameters except the IP address and the APM server for a SQL Server application monitor. When the IP address of the SQL Server host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a SQL Server application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page opens.

3. Click the Modify icon for the SQL Server application monitor you want to modify.

The page for modifying the SQL Server application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a SQL Server application monitor."

5. Click OK.

Viewing the SQL Server application monitor report

After a SQL Server application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for the SQL Server application by viewing the monitor report.

To access a SQL Server application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a SQL Server application monitor to display the report.

Figure 64 shows part of a SQL Server application monitor report.

Figure 64 Part of a SQL Server application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the SQL Server application.

· IP Address—IP address of the SQL Server host.

· Application Type—Type of the monitored application, which is always SQL Server.

· Version—Version of the SQL Server application.

· Port—Service port of the SQL Server application.

· Last Polling Time—Time when APM last polled the SQL Server application.

· Relationship—Click the Relationship icon to view dependencies between the SQL Server application and other applications in the dependency topology. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarm—Latest five unrecovered alarms on SQL Server host. The alarm level is identified by color: yellow for minor alarms, orange for major alarms, and red for critical alarms. This field is not displayed if no alarm is generated by the SQL Server application.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the SQL Server application in the last polling interval.

¡ Click the Weekly History icon to view the availability of the SQL Server application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the SQL Server application in the last 30 days.

· Available Time—Total amount of time that the SQL Server application was available after 00:00 today.

· Unavailable Time—Total amount of time that the SQL Server application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the SQL Server application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the SQL Server application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed when its value is 0.

Memory Usage

The Memory Usage area contains the following fields:

· Total Memory—Total size of the dynamic memory used by the SQL Server application in the last polling interval.

· SQL Buffer—Size of the dynamic memory used by the SQL Server application for SQL cache in the last polling interval. Click the History Record icon to view the history graph of the SQL buffer.

· Optimizer Memory—Size of the dynamic memory used by the SQL Server application to query optimization in the last polling interval. Click the History Record icon to view the history graph of the optimizer memory.

· Lock Memory—Size of the dynamic memory used by the SQL Server application for locks in the last polling interval. Click the History Record icon to view the history graph of the lock memory.

· Connection Memory—Size of the dynamic memory used by the SQL Server application to maintain connections in the last polling interval. Click the History Record icon to view the history graph of the connection memory.

· Granted Workspace Memory—Size of the dynamic memory that the SQL Server application allocated for processes to perform operations, such as hashing, sorting, copying, and creating indexes in the last polling interval.

· Undetermined Memory—Number of processes that were waiting for the permissions to use the workspace memory in the last polling interval.

· Memory Grants Outstanding—Number of processes that were permitted to use the workspace memory in the last polling interval.

Buffer Management

The Buffer Management area contains the following fields:

· Buffer Hit Ratio—How often the required pages have been found in the buffer pool without reading from the disk in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the buffer hit ratio.

¡ Click the History Record icon to view the history graph of the buffer hit ratio.

· Page Lookups/Min—Number of requests to search for pages in the buffer pool per minute in the last polling interval. Click the History Record icon to view the history graph of the page lookups per minute.

· Page Reads/Min—Number of database pages that were read from the disk per minute in the last polling interval. Click the History Record icon to view the history graph of the page reads per minute.

· Page Writes/Min—Number of database pages that were written to the disk per minute in the last polling interval. Click the History Record icon to view the history graph of the page writes per minute.

· Total Pages—Total number of pages in the SQL Server buffer, including stolen pages, available pages, and database pages in the last polling interval.

· Database Pages—Number of database pages in the buffer pool in the last polling interval.

· Free Pages—Available pages in the buffer pool in the last polling interval.

· Disk Reads—Total number of disk reads since the connection started.

· Disk Writes—Total number of disk writes since the connection started.

Connection Statistics

The Connection Statistics area contains the following fields:

· Connection Time—Time consumed when APM established the connection with the SQL Server application in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the connection time.

¡ Click the History Record icon to view the history graph of the connection time.

· Active Connections—Number of connections between the SQL Server application and its users in the last polling interval. Click the History Record icon to view the history graph of active connections.

· Logins/sec—Number of newly established connections per second in the last polling interval. Click the History Record icon to view the history graph of logins per second.

· Logouts/sec—Number of terminated connections per second in the last polling interval. Click the History Record icon to view the history graph of logouts per second.

· Sessions—Number of sessions of the SQL Server.

· Running Sessions—Number of running sessions of the SQL Server.

Buffer Details

The Buffer Details area contains the following fields:

· Cache Hit Ratio—How often the required data has been found in the cache in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the cache hit ratio.

¡ Click the History Record icon to view the history graph of the cache hit ratio.

· Cache Objects in Use—Number of cache objects that were being used in the last polling interval. Click the History Record icon to view the history graph of the cache objects being used.

· Cache Object Counts—Number of cache objects in the cache in the last polling interval. Click the History Record icon to view the history graph of the cache object count.

· Cache Pages—Number of pages that the cache objects were using in the last polling interval. The size of each page is 8K. Click the History Record icon to view the history graph of cache pages.

Lock Details

The Lock Details area contains the following fields:

· Lock Requests/sec—Number of lock requests and the lock conversions received by the SQL Server application per second in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the lock requests per second.

¡ Click the History Record icon to view the history graph of the lock requests per second.

· Lock Waits/sec—Number of waiting lock requests per second in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the lock waits per second.

¡ Click the History Record icon to view the history graph of the lock waits per second.

· Lock Timeouts/sec—Number of lock requests that timed out per second in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the lock timeouts per second.

¡ Click the History Record icon to view the history graph of the lock timeouts per second.

· Number of Deadlocks/sec—Number of lock requests that resulted in deadlocks per second in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the number of deadlocks per second.

¡ Click the History Record icon to view the history graph of the number of deadlocks per second.

· Average Wait Time—Average waiting time for each lock request in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the average wait time.

¡ Click the History Record icon to view the history graph of the average wait time.

· Locks—Total number of locks.

· Deadlocks—Number of deadlocks.

· Lock TimeOut—Lock timeout time. The value of -1 indicates that the lock never times out.

· Table Locks—Number of table locks.

SQL Statistics

The SQL Statistics area contains the following fields:

· Batch Requests/Min—Number of Transact-SQL command batches that the SQL Server application received per minute in the last polling interval. A high value of this index indicates good throughput. Click the History Record icon to view the history graph of the batch requests per minute.

· SQL Compilations/Min—Times of SQL compilations per minute in the last polling interval. This value is in steady state after the activity of the SQL Server user becomes stable. Click the History Record icon to view the history graph of the SQL compilations per minute.

· SQL Recompilations/Min—Times of SQL recompilations per minute in the last polling interval. Click the History Record icon to view the history graph of the SQL recompilations per minute.

· Auto Param Attempts/Min—Times of the auto-parameterization attempts per minute in the last polling interval. The auto-parameterization attempt progress happens whenever the SQL Server instance tries to replace some characters with the parameters to parameterize Transact-SQL requests. To the similar requests, this progress can reuse the operation plan saved in the cache. Click the History Record icon to view the history graph of the auto parameter attempts per minute.

· Auto Param Failures/Min—Times of the failed auto-parameterization attempts per minute in the last polling interval. The value should be small. Click the History Record icon to view the history graph of the auto parameter failures per minute.

Latch Details

The Latch Details area contains the following fields:

· Latch Waits/Min—Number of waiting latch requests per second in the last polling interval. Click the History Record icon to view the history graph of the latch waits per minute.

· Average Latch Wait Time—Average waiting time (in millisecond) for latch requests in the last polling interval. Click the History Record icon to view the history graph of the average latch wait time.

Access Method Details

The Access Method Details area contains the following fields:

· Full Scans/Min—Times of unrestricted base-table or full-index scans per minute in the last polling interval. Click the History Record icon to view the history graph of the full scans per minute.

· Range Scans/Min—Times of range scans by using indexes per minute in the last polling interval. Click the History Record icon to view the history graph of the range scans per minute.

· Probe Scans/Min—Number of probe scans to directly find at most one single qualified row in an index or base table per second in the last polling interval. Click the History Record icon to view the history graph of the probe scans per minute.

Waiting Tasks

The Waiting Tasks area contains the following field:

· Waiting Tasks—Number of tasks that are waiting for processor, I/O, or memory resources. Click the History Record icon to view the history data for waiting tasks.

Database I/O

The Database I/O area contains the following field:

Database I/O—Transfer rate, in megabytes per second, of data from memory to disk, disk to memory, or disk to disk.

Resource Waits

The Resource Waits area contains the following fields:

· Wait Category—Categories that accumulate wait type statistics.

· Wait Time (ms/sec)—Wait time in milliseconds per second for all tasks that are waiting for one or more resources in the wait category since the last update interval.

· Average Waiter Count—Number of tasks that are waiting for one or more resources in the wait category at a typical moment during the last sample interval.

· Cumulative Wait Time—Total amount of time that tasks have waited.

Data File I/O

The Data File I/O area contains the following fields:

· Database—Name of the database.

· File Name—Name of the database file.

· MB/sec Read—Most recent read activity, in megabytes per second, for the database file.

· MB/sec Written—Most recent write activity, in megabytes per second, for the database file.

· Size—Size of the database file.

· Response Time—Average response time, in milliseconds, of the most recent read-and-write activity to the database file.

% Processor Time

The % Processor Time area contains the following field:

% Processor Time—Percentage of the time that the processor spends to execute non-idle threads for the instance across all CPUs. Click the History Record icon to view the history data for the processor time.

Blocked Process Number

The Blocked Process Number area contains the following field:

· Blocked Process Number—Number of blocked processes.

Application Traffic

APM collects SQL Server traffic based on the IP address of the host and the traffic collection port used by the application.

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by the SQL Server application over the last 1 hour in the last polling interval.

· Today's Traffic—Total traffic sent and received by the SQL Server application since 00:00 today in the last polling interval.

Activity User Tasks

The Activity User Tasks area contains the following fields:

· Session ID—Unique integer assigned to a user connection when the connection is established.

· User Process—Displays 0 for a system process and 1 for a user process.

· Login—SQL Server login name under which the session is currently executing.

· Database—Name of the database.

· Task State—State of the task.

· Command—The kind of command.

· Application—Name of the application program that created the connection.

· Wait Time—Time, in milliseconds, in which this task is waiting for a resource. When the task is not waiting, the wait time is 0.

· Wait Type—Name of the wait type.

· Wait Resource—Name of the resource that is needed.

· Blocked By—ID of the session that is blocking the task.

· Memory Use (KB)—Amount of memory, in kilobytes, that is being used by the task.

· Host Name—Name of the computer that made the connection to the instance of SQL Server.

· Workload Group—Name of the Resource Governor workload group for the session.

Job Details

The Job Details area contains the following fields:

· Name—Name of the job that has or has not run in the last polling interval.

· Enabled—Indicates whether the job is enabled.

· Result—Result of the job. An en dash (-) indicates that the job has never run.

· Date—Date when the job started running.

· Time—Time when the job started running.

· Duration—Running duration of the job.

Database Status

The Database Status area contains the following fields:

· Database—Database name.

· Database Status—Status of the database.

· Database Create Date—Date when the database was created.

Database Details

The Database Details area contains the following fields:

· Database—Name of the running database in the SQL server application. "_Total" indicates statistics for all databases.

· Size—Disk space for the database.

· Used Size—Size of the database space that is used.

· Free Size—Size of the database space that is not used.

· Database Usage Ratio—Percentage of the used database space to the total database space.

· Data File Size—Size of the data file.

· Data File Path—Path where the data file is located.

· Data File Number—Number of the data files.

· Transactions—Number of transactions that the database started per minute.

· Active Transactions—Number of active transactions of the database.

You can click the History Record icon to view the history graph of a monitor index.

Database Log Details

The Database Log Details contains the following fields:

· Database—Name of the database that the SQL server application runs. The value Total indicates that information about all databases is collected.

· Log File—Disk space occupied by database log files.

· Log Files Used—Size of used log files in the database.

· Log File Usage Ratio—Usage ratio of the log files in the database. Log Files Usage Ratio = Log Files Used/Log Files x 100%.

· Log Writes—Times of writing the log to the log file per minute.

· Log Write Waits—Number of logs that were waiting to be written to the log files.

· Log Write Wait Time—Total waiting time before the log was written to the log file.

You can click the History Record icon to view the history graph of a monitor index, and click the Set Threshold icon to set alarm thresholds for a monitor index.

Top 10 SQL by Execution Durations

The Top 10 SQL by Execution Durations area displays top 10 SQL statements by accumulated execution duration.

The Top 10 SQL by Execution Durations area contains the following fields:

· SQL—SQL statement.

· Cumulative Execution Duration—Total duration used for parsing and executing the SQL statement.

· Cumulative CPU Time—Duration that parsing and executing the SQL statement occupies the CPU.

· Logical Reads—Number of logical reads of the SQL statement.

· Physical Reads—Number of physical reads of the SQL statement.

· Executions—Number of times that the SQL statement is executed.

Top 10 SQL By Cumulative CPU Time

The Top 10 SQL By Cumulative CPU Time area contains the following fields:

· SQL—SQL statement.

· Cumulative Execution Duration—Time taken to parse and execute the SQL statement.

· Cumulative CPU Time—CPU time taken to parse and execute the SQL statement.

· Logical Reads—Number of times for which the SQL statement has been logically read.

· Physical Reads—Number of times for which the SQL statement has been physically read.

· Executions—Number of times for which the SQL statement has been executed.

MySQL

MySQL is an open source DBMS that directly impacts the service performance. APM supports monitoring MySQL applications.

Adding a MySQL application monitor

APM can locally or remotely monitor MySQL applications through JDBC. When you add MySQL application monitors, follow these guidelines:

· To locally monitor SQL Server applications, install agents on the hosts where MySQL applications are deployed. For more information about installing agents, see "APM agent management."

· Obtain the username and password of the user who has the MySQL administrator's privileges.

· Add MySQL hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the MySQL application, make sure at least one probe is configured in APM. After a MySQL application monitor is added, APM sends the IP address and service port of the monitored MySQL application to the probes for traffic collection.

To add a MySQL application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Management > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click MySQL of the Database Server Monitor class.

The page for adding a MySQL application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the MySQL application to be monitored is installed. APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform. If the host is already added to the IMC platform, you can also click Select, and then select the host from the Select Devices window. For information about selecting a host, see "Quick start."

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Application Monitor Port—Enter the service port number for MySQL, 3306 by default. This field is available only when you select Disable from the Use Template list.

¡ Traffic Collection Port—Enter the service port number for MySQL. This field is displayed only when at least one probe is configured for APM and when you select Enable from the Use Template list.

¡ Username—Enter the username of the MySQL administrator. This field is available only when you select Disable from the Use Template list.

¡ Password—Enter the password of the MySQL administrator. This field is available only when you select Disable from the Use Template list.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of MySQL applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ APM Server—Select an APM server to monitor the application. The option is in server-address (application-type:n/N) format. The letter n indicates the number of the selected type of applications monitored on the APM server. The letter N indicates the number of all types of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that MySQL depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology. APM automatically adds the dependencies between MySQL and operating system applications by IP address and displays their dependencies in the application topology.

¡ Application Group—Specify an application group for the MySQL application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

5. Click OK.

Modifying a MySQL application monitor

Authorized users can modify all parameters except the IP address and the APM server for a MySQL application monitor. When the IP address of the MySQL host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify a MySQL application monitor:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The page displays the application types that can be monitored by APM.

3. Click the Modify icon for the MySQL application monitor you want to modify.

The page for modifying the MySQL application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding a SQL Server application monitor."

5. Click OK.

Viewing MySQL application monitor report

After a MySQL application monitor is added, APM collects index data of the application, and calculates its availability and health status. You can obtain monitor indexes for the MySQL application by viewing the monitor report.

To access a MySQL application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of a MySQL application monitor to display the report.

Figure 65 shows part of a MySQL application monitor report.

Figure 65 Part of a MySQL application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the MySQL application.

· IP Address—IP address of the MySQL host.

· Application Type—Type of the monitored application, which is always MySQL.

· MySQL Version—Version of the MySQL application.

· Port—Service port of the MySQL application.

· Basic Directory—MySQL installation path recorded in the MySQL application.

· Data Directory—Data file storage directory in the MySQL application.

· Last Polling Time—Time when APM last polled the MySQL application.

· Relationship—Click the Relationship icon to view dependencies between the MySQL application and other applications in the dependency topology. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarm—Latest five unrecovered alarms on the MySQL host. The alarm level is identified by color: yellow for minor alarms, orange for major alarms, and red for critical alarms. This field is not displayed if no alarm is generated by the MySQL application.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the MySQL application in the last polling period.

¡ Click the Weekly History icon to view the availability of the MySQL application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the MySQL application in the last 30 days.

· Available Time—Total amount of time that the MySQL application was available after 00:00 today.

· Unavailable Time—Total amount of time that the MySQL application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the MySQL application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the MySQL application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed when its value is 0.

Thread Exclusive Memory

The Thread Exclusive Memory area contains the following fields:

· Total Thread Exclusive Memory—Total memory that is exclusive to threads.

· Thread Stack Buffer—Size of the buffer that stores identity information of each thread.

· Sort Buffer—Size of the buffer used for sorting files.

· Join Buffer—Size of the buffer used for joining two or more tables.

· Read Buffer—Size of the buffer used for reading data in order.

· Random Read Buffer—Size of the buffer used for randomly reading data.

· Temporary Table Buffer—Size of the buffer used for operating temporary tables.

Global Shared Memory

The Global Shared Memory area contains the following fields:

· Total Global Shared Memory—Total memory that is globally shared.

· Queue Buffer—Size of the buffer used for request results.

· Thread Buffer—Size of the buffer that stores idle connection threads.

· Table Buffer—Size of the buffer that stores information about file handles in the table file.

· Table Definition Buffer—Size of the buffer that stores table definition information.

· Binary Log Buffer—Size of the buffer that stores information about binary logs caused by data change.

· Key Buffer—Size of the buffer used for index blocks.

· InnoDB Log Buffer—Size of the buffer used for InnoDB transaction logs.

· InnoDB Data and Index Buffer—Size of the buffer used for InnoDB data and index blocks.

· InnoDB Dictionary Buffer—Size of the buffer used for InnoDB dictionary information.

Response Time

The Response Time area contains the following fields:

· Response Time—Response time of the MySQL application in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the response time.

¡ Click the History Record icon to view the history graph of the response time.

· Connection Timeout—Time before the connection times out. Click the History Record icon to view the history graph of the connection timeout.

Request Statistics

The Request Statistics area contains the following fields:

· Requests/s—Number of connection requests that the MySQL application received per second in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the requests received per second.

¡ Click the History Record icon to view the history graph of the requests received per second.

· Receive Rate—Bandwidth that the MySQL application consumed to receive data from all clients per second in the last polling interval. Click the History Record icon to view the history graph of the receive rate.

· Send Rate—Bandwidth that the MySQL application consumed to send data to all clients per second in the last polling interval.

¡ Click the Set Threshold icon to set alarm thresholds for the send rate.

¡ Click the History Record icon to view the history graph of the send rate.

Connection Statistics

The Connection Statistics area contains the following fields:

· Connections—Total number of successful connections from the MySQL application start time to the last polling time. Click the History Record icon to view the history graph of the connections.

· Aborted Connections—Total number of failed connections from the MySQL application start time to the last polling time. Click the History Record icon to view the history graph of the aborted connections.

· Aborted Clients—Total number of connections terminated by the MySQL server from the MySQL application start time to the last polling time. Click the History Record icon to view the history graph of the aborted clients.

· Connections Per Second—Number of connection attempts per second.

· Established Connections Per Second—Number of established connections per second.

· Connection Cache Hit Ratio—Ratio of the connections read from the cache to the total connections.

· Max Allowed Connections—Maximum number of allowed connections.

· Actual Max Connections—Actual maximum number of connections.

Thread Details

The Thread Details area contains the following fields:

· Running Threads—Number of running threads in the MySQL application in the last polling interval. Click the History Record icon to view the history graph of running threads.

· Buffered Threads—Number of buffered threads in the thread cache in the last polling interval. Click the History Record icon to view the history graph of buffered threads.

· Thread Buffer Size—Number of threads that can be buffered in the thread cache.

Key Details

The Key Details area contains the following fields:

· Key Hit Ratio—Buffer hit ratio for keys in the last polling interval. A larger value indicates a better result.

¡ Click the Set Threshold icon to set alarm thresholds for the key hit ratio. An alarm is generated when the index value is less than or equal to the threshold value.

¡ Click the History Record icon to view the history graph of the key hit ratio.

· Key Writes Hit Ratio—Ratio of key writes to the key write requests.

· Key Buffer Used—Size of the key buffer used by the MySQL application in the last polling interval. Click the History Record icon to view the history graph of the key buffer used.

· Key Buffer—Total size of the key buffer for the MySQL application in the last polling interval.

· Index Reads—Number of key block reads from the hard disk.

· Index Reads/Min—Number of key block reads from the hard disk per minute.

· Index Writes—Number of key block writes from the hard disk.

· Index Writes/Min—Number of key block writes to the hard disk per minute.

Buffer Details

The Buffer Details area contains the following fields:

· Query Hit Ratio—Ratio of key value reads from the buffer to the number of query attempts.

· Queue Buffer—Memory allocated for buffering the request result.

· Queue Buffer Limit—Maximum memory used for storing the buffer result.

· Cache Queries—Number of query commands in the cache.

Table Lock Statistics

The Table Lock Statistics area contains the following fields:

· Table Locks Immediately Released/sec—Number of immediately released table locks per minute in the last polling interval. Click the History Record icon to view the history graph of the table locks immediately released per minute.

· Table Locks Wait/sec—Number of waiting table locks in the last polling interval. Click the History Record icon to view the history graph of the table locks waits per minute.

SQL Operation Statistics/min

The SQL Operation Statistics/min area contains the following fields:

· Deletes—Number of Delete statements executed by the MySQL application per minute in the last polling interval. Click the History Record icon to view the history graph of the Delete statements executed by the MySQL application per minute.

· Adds—Number of Insert statements executed by the MySQL application per minute in the last polling interval. Click the History Record icon to view the history graph of the Add statements executed by the MySQL application per minute.

· Queries—Number of Select statements executed by the MySQL application per minute in the last polling interval. Click the History Record icon to view the history graph of the Query statements executed by the MySQL application per minute.

· Updates—Number of Update statements executed by the MySQL application per minute in the last polling interval. Click the History Record icon to view the history graph of the Update statements executed by the MySQL application per minute.

InnoDB Buffer Hit Ratio

The InnoDB Buffer Hit Ratio area contains the following field:

Hit Ratio—Hit ratio of InnoDB buffer.

Transactions Per Second

The Transactions Per Second area contains the following field:

Transactions Per Second—Number of transactions handled per second.

Application Traffic

APM collects MySQL traffic based on the IP address of the host and the traffic collection port used by the application.

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by the MySQL application over the last 1 hour in the last polling interval.

· Today's Traffic—Total traffic sent and received by the MySQL application since 00:00 today in the last polling interval.

Database Details

The Database Details area contains the following fields:

· Database—Name of the running database on the MySQL application.

· Size—Size of disk space for the database.

· Tables—Number of tables in the database.

Oracle

Oracle Database is a database management system developed by Oracle Corporation. The performance and stability affects the service applications. APM supports monitoring Oracle applications.

Adding an Oracle application monitor

APM can monitor Oracle through agents or JDBC. When you add application monitors for Oracle, follow these guidelines:

· To monitor an Oracle application through an agent, you must deploy the agent on the Windows or Linux operating system where the Oracle application is installed.

· To monitor an Oracle application through JDBC, obtain the username and password of the user who has the Oracle administrator's privileges.

· You must identify whether the Oracle application has used RAC and identify the Oracle SID to be monitored.

· Add Oracle hosts to the IMC platform so that APM can obtain and display network connections of the hosts and their access devices in the application topology. For more information about adding hosts to the IMC platform, see H3C Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide.

· To view traffic statistics in the monitor report of the Oracle application, make sure at least one probe is configured in APM. After an Oracle application monitor is added, APM sends the IP address and service port of the monitored Oracle application to the probes for traffic collection.

To add an Oracle application monitor:

1. Click the Resource tab.

2. Open the Add Application page by using one of the following methods:

¡ From the navigation tree, select Application Management > Add Application.

The page displays all application types that can be monitored by APM.

¡ From the navigation tree, select Application Manager > Application Monitor, and then click Add on the application monitor list page.

3. Click Oracle of the Database Server Monitor class.

The page for adding an Oracle application monitor opens.

4. Configure the following parameters:

¡ IP Address—Enter the IP address of the host on which the Oracle application to be monitored is installed. If the host is already added to the IMC platform, you can also click Select, and then select the host from the Select Devices window. For information about selecting a host, see "Quick start." APM automatically checks the specified IP address and associates the application monitor with the host managed in the IMC platform.

¡ Name—Enter a unique application monitor name. As a best practice, name the application monitor as application type_host IP address.

¡ Use Template—Select Enable or Disable from the list.

¡ Description—Enter a description for the application monitor.

¡ Application Monitor Port—Enter the service port number for the Oracle application. The default is 1521. This field is displayed only when you select Disable from the Use Template list.

¡ Traffic Collection Port—Enter the service port number for the Oracle application. This field is displayed only when at least one probe is configured for APM. This field is displayed only when you select Disable from the Use Template list.

¡ Polling Interval (min)—Select a polling interval for the application monitor. Options are 1, 2, 3, 4, 5, 10, 20, and 30. The default polling interval is 5 minutes. A shorter polling interval improves real-time data accuracy at the expense of system resources. This field is displayed only when you select Disable from the Use Template list.

¡ Monitor Type—Select the Oracle running type. Options are stand-alone and rac. This field is displayed only when you select Disable from the Use Template list.

¡ Database Instance Name—Enter the instance name for the Oracle application. This field is displayed only when you select Disable from the Use Template list.

¡ Username—Enter the username of the Oracle administrator. If the username is sys, enter sys as sysdba in this field. This field is displayed only when you select Disable from the Use Template list.

¡ Password—Enter the password of the Oracle administrator. This field is displayed only when you select Disable from the Use Template list.

¡ Contact—Enter contact information, such as the name, email address, and telephone number. The default is the username of the operator who created the application monitor. This field is displayed only when you select Disable from the Use Template list.

¡ APM Server—Select an APM server to monitor the application. The options are in server-address (application-type:n/N) format. The letter n indicates the number of Oracle applications monitored on the APM server. The letter N indicates the total number of applications monitored on the APM server. Server address 127.0.0.1 indicates that APM and the IMC platform are deployed on the same server.

¡ Related Applications—Click Add next to this field. On the Select Application window, enter a partial or complete name to filter applications, select the applications that Oracle depends on, and then click OK.

Operating system applications cannot be selected. Operators can view all dependencies of the application in the dependency topology. APM automatically adds the dependencies between Oracle and operating system applications by IP address and displays their dependencies in the application topology.

¡ Application Group—Specify an application group for the Oracle application.

- To specify an existing application group, click Add, select an application group, and then click OK.

- To specify a new application group, click Add Application Group, configure the application group settings, and then click OK.

¡ Detect Application—Select this parameter if you want to enable application detection. Application detection enables APM to verify connectivity to the application by using the previous parameter settings, and to determine whether to add the application monitor based on the verification result. APM adds the application monitor only when it can connect to the application. When this parameter is not specified, APM adds the application monitor without verifying the connection.

5. Click OK.

Modifying an Oracle application monitor

Authorized users can modify all parameters except the IP address and the APM server for an Oracle application monitor. When the IP address of the Oracle host changes, operators must add a new application monitor for the host. The new application monitor cannot inherit the history data from the previous application monitor.

To modify an Oracle application monitor:

1. Click the Resource tab.

2. From the navigation tree, click Application Manager > Application Monitor.

The page displays all application types that can be monitored by APM.

3. Click the Modify icon for the Oracle application monitor you want to modify.

The page for modifying the Oracle application monitor opens.

4. Modify the parameters as needed, except the IP address and the APM server.

For more information about parameter settings, see "Adding an Oracle application monitor."

5. Click OK.

Viewing the Oracle application monitor report

After an Oracle application monitor is added, APM collects index data of the application, and calculates its availability and health status, and updates the monitor report. The report shows the index values obtained from the most recent polling of the application.

To view the Oracle application monitor report:

1. Click the Resource tab.

2. From the navigation tree, select Application Manager > Application Monitor.

The application monitor list page displays all application monitors.

3. Click the name of an Oracle application monitor to display the report.

Figure 66 shows part of an Oracle application monitor report. The Oracle application monitor report contains the Summary, Objects, Tablespace, Session, Top10 SQL, and Parameter tabs.

Figure 66 Part of an Oracle application monitor report

Monitor Information

The Monitor Information area contains the following fields:

· Name—Application monitor name.

· Health Status—Health status of the Oracle application.

· IP Address—IP address of the Oracle host.

· Application Type—Type of the monitored application, which is always Oracle.

· Port—Service port of the Oracle application.

· Port Status—Status of the Oracle application service port.

· Version—Version number of Oracle application.

· Start Time—Date and time when the Oracle application started.

· Bits—Number of bits for the Oracle application, 32 or 64.

· Character Set—Character set for the Oracle application.

· Last Polling Time—Time when APM last polled the Oracle application.

· Relationship—Click the Relationship icon to view dependencies between the Oracle application and other applications in the dependency topology. For more information about dependency topologies, see "Topology and application group management."

· Top5 Unrecovered Alarm—Latest five unrecovered alarms on the Oracle host. The alarm level is identified by color: yellow for minor alarms, orange for major alarms, and red for critical alarms. This field is not displayed if no alarm is generated by the Oracle application.

Availability Today

The Availability Today area contains the following fields:

· Current Availability—Availability of the Oracle application.

¡ Click the Weekly History icon to view the availability of the Oracle application in the last 7 days.

¡ Click the Monthly History icon to view the availability of the Oracle application in the last 30 days.

· Available Time—Total amount of time that the Oracle application was available after 00:00 today.

· Unavailable Time—Total amount of time that the Oracle application was unavailable after 00:00 today.

· Inaccessible Time—Total amount of time that the Oracle application was inaccessible after 00:00 today.

· Unmanaged Time—Total amount of time that the Oracle application was unmanaged after 00:00 today.

The statistics collection started when the application monitor was added. An availability time field is not displayed when its value is 0.

Oracle Detail

The Oracle Detail area contains the following fields:

· Creation Time—Time when Oracle application installation was completed.

· Open Mode—Current open mode for the Oracle application. Open modes include READ ONLY and READ WRITE.

· Logging Mode—Current logging mode for the Oracle application. The following logging modes are available:

¡ ARCHIVELOG—The old log file is automatically copied to the specified path and cannot be overwritten by the new log file during log file switching.

¡ NOARCHIVELOG—The old log file is overwritten by the new log file during log file switching.

· Size—Size of disk space used by all the datafiles in the Oracle application.

· Block Size—Default standard block size for the Oracle application.

· Average Execution Times—Average number of times that each SQL statement in the Oracle application was executed.

¡ Click the Set Threshold icon to set alarm thresholds for the average execution times.

¡ Click the History Record icon to view the history graph of the average execution times.

· Reads—Number of times that the Oracle application read data blocks from the disk. Click the History Record icon to view the history graph for this field.

· Writes—Number of times that the Oracle application wrote data blocks to the disk. Click the History Record icon to view the history graph for this field.

· Disk/Memory Sort Ratio—Disk/memory sorting ratio. It is obtained by using the formula: Disk sorting attempts/Memory sorting attempts x 100%. Click the History Record icon to view the history graph of the disk/memory sorting ratio.

· Row Link/Row Mitigation Count—Number of row links and number of row mitigations.

· Forcible Log Switch Time—Time when the Oracle application was forced to perform Redo log file switching.

· Database Name—Name of the Oracle database.

· Physical Memory—Physical memory size of the Oracle database server.

· Transactions Per Second—Average number of transactions executed per second.

· Flashback On—Flashback setting:

¡ YES—Flashback is on.

¡ NO—Flashback is off.

¡ RESTORE POINT ONLY—Flashback is on but one can only flash back to reliable restore points.

· Locks—Number of locks in the database.

· Deadlocks—Number of deadlocks in the database.

· Weekly Growth Rate of Archived Logs—Weekly growth rate of achived logs in percentage in the database.

Connection Time

The Connection Time area contains the following field:

· Connection Time—Amount of time APM took to establish connectivity with the Oracle application.

¡ Click the Set Threshold icon to set alarm thresholds for the connection time.

¡ Click the History Record icon to view the history graph of the connection time.

SGA Details

You can click the History Record icon to view the history graph for each field.

The SGA Details area contains the following fields:

· Buffer—Size of buffer cache in SGA.

· Fixed Area—Size of the fixed area in SGA. The fixed area, typically in small size, contains control information for other SGA regions.

· Database Buffer—Size of the library cache in SGA.

· Dictionary Buffer—Size of the dictionary cache in SGA.

· Dictionary Ratio—Ratio of the used dictionary buffer to the total dictionary buffer.

· SQL Area—Size of the SQL area in SGA.

· Shared SQL Butter Ratio—Ratio of the used shared SQL buffer to the total shared SQL buffer.

· SGA Ratio—Ratio of the used SGA buffer to the total SGA buffer.

· SGA Used Size—SGA used space size

SGA State

The System Global Area (SGA) is a shared memory space allocated to the Oracle application.

The SGA State area contains the following fields:

· Buffer Hit Ratio—Percentage of times that the requested information was found in the buffer cache.

¡ Click the Set Threshold icon to set alarm thresholds for the buffer hit ratio.

¡ Click the History Record icon to view the history graph of the buffer hit ratio.

· Dictionary Hit Ratio—Percentage of times that the requested information was found in the dictionary cache.

¡ Click the Set Threshold icon to set alarm thresholds for the dictionary hit ratio.

¡ Click the History Record icon to view the history graph of the dictionary hit ratio.

· Library Hit Ratio—Percentage of times that the requested information was found in the library cache.

¡ Click the Set Threshold icon to set alarm thresholds for the library hit ratio.

¡ Click the History Record icon to view the history graph of the library hit ratio.

· Free Memory—Free memory in SGA. Click the History Record icon to view the history graph of the free memory.

Large Pool

You can click the History Record icon to view the history graph for each field.

The Large Pool area contains the following fields:

· Large Pool—Total size of the large pool.

· Large Pool Free Size—Free space size of the large pool.

· Large Pool Used Size—Used space size of the large pool.

· Large Pool Ratio—Ratio of the used large pool size to the total large pool size.

Java Pool

You can click the History Record icon to view the history graph for each field.

The Java Pool area contains the following fields:

· Java Pool—Total size of the Java pool.

· Java Pool Free Size—Free space size of the Java pool.

· Java Pool Used Size—Used space size of the Java pool.

· Java Pool Ratio—Ratio of the used Java pool size to the total Java pool size.

Shared Pool

You can click the History Record icon to view the history graph for each field.

The Shared Pool area contains the following fields:

· Shared Pool—Total size of the shared pool.

· Shared Pool Free Size—Free space size of the shared pool.

· Shared Pool Used Size—Used space size of the shared pool.

· Shared Pool Ratio—Ratio of the used shared pool size to the total shared pool size.

REDO Log Buffer

You can click the History Record icon to view the history graph for each field.

The REDO Log Buffer area contains the following fields:

· REDO Log Buffer—REDO log buffer size.

· REDO Request Failure Ratio—Ratio of the failed REDO requests to the total REDO requests.

· REDO Writes/Sec—Number of REDO writes in the most recent polling interval.

· REDO Block Writes/Sec—Number of REDO blocks written per second in the most recent polling interval.

· REDO Entries/Sec—Number of REDO entries per second in the most recent polling interval.

Connection Information

The Connection Information area contains the following fields:

· Current Connections—Number of connections used. Click the History Record icon to view the history graph of the current connections.

· Max. Connections—Maximum number of connections allowed by the Oracle application. If the number of connections reaches the maximum number, new connections cannot be established.

PGA Statistics

A Program Global Area (PGA) is a non-shared memory area allocated to each process in the Oracle application when the process starts.

Application Traffic

APM collects Oracle application traffic based on the IP address of the host and the traffic collection port used by the application.

The Application Traffic area contains the following fields:

· Last Hour's Traffic—Total traffic sent and received by the Oracle application over the last 1 hour.

· Today's Traffic—Total traffic sent and received by the Oracle application since 00:00 today.

Instance Efficiency Percentages

You can click the History Record icon to view the history graph for each field.

The Instance Efficiency Percentages area contains the following fields:

· Buffer Hit Ratio—Buffer hit ratio of the Oracle application.

· Library Cache Hit Ratio—Library cache hit ratio of the Oracle application.

· Latch Hit Ratio—Latch hit ratio of the Oracle application.

· No Wait Ratio for Obtaining Redo Log Buffer—Percentage of times that the Oracle application obtained Redo log buffer without waiting.

· No Wait Ratio for Obtaining Data from Memory—Percentage of times that the Oracle application obtained data from memory without waiting.

· Execute to Parse Ratio—Percentage of executed SQL statements to parsed SQL statements.

· Parse Efficiency—Parse efficiency of SQL statements.

· Running Efficiency—Running efficiency of SQL statements.

· Memory Sort Ratio—Percentage of times for sorting SQL statements in the memory.

· Disk Sorts /Sec—Number of disk sorts per second in the most recent polling interval.

· Memory Sorts /Sec—Number of memory sorts per second in the most recent polling interval.

· Flash Recovery Area Usage Ratio—Usage ratio of the Oracle flash recovery area.

· CPU Usage Ratio—Ratio of the CPU used to execute and parse SQL statements.

· PGA Hit Ratio—Hit ratio of the Process Global Area.

· PGA Ratio—Ratio of the used PGA buffer to the total PGA buffer.

Load Profile

You can click the History Record icon to view the history graph for each field.

The Load Profile area contains the following fields:

· Logical Chunk Reads/Sec—Number of data blocks read from the buffer cache per second.

· Physical Chunk Reads/Sec—Number of data blocks read from the disk per second.

· Physical Chunk Writes/Sec—Number of data blocks written to the disk per second.

· Chunk Changes/Sec—Number of data blocks modified per second.

· Parses/Sec—Number of SQL statements parsed per second.

· Hard Parses/Sec—Number of SQL statements hard parsed per second.

· Operations/Sec—Number of SQL statements executed per second.

· Logins/Sec—Number of logins per second.

· Hard Parse Ratio—Hard parse ratio of SQL statements.

· Soft Parse Ratio—Soft parse ratio of SQL statements.

Global Cache Information

The Global Cache Information area contains the following fields:

· Remote Cache Access Ratio—Remote cache access ratio when the Oracle application runs in a RAC.

· Disk Cache Access Ratio—Disk cache access ratio when the Oracle application runs in a RAC.

· Node Inline Traffic—Inline traffic among nodes when the Oracle application runs in a RAC.

· Local Cache Access Ratio—Local cache access ratio when the Oracle application runs in a RAC.

· Logins/Sec—Number of logins for the Oracle application per second.

DB Time

The DB Time area contains the following field:

· DB Time—Amount of time used by the Oracle application to handle non-idle waits and database computation. This field is recorded in the Automatic Workload Repository (AWR).

Database Time Zone

The Database Time Zone area contains the following fields:

· Database Time Zone—Time zone configured for the database.

· Session Time Zone—Time zone used when the client is connected to the Oracle database.

· Time—Database time when data was most recently collected.

Transactions in Current Rollback Segment

The Transactions in Current Rollback Segment area contains the following fields:

· Name—Transaction name.

· Session ID—ID of the session to which the transaction belongs.

· SQL—SQL statement executed by the transaction.

Rollback

The Rollback area contains the following fields:

· Segment—Name of the rollback segment.

· Tablespace—Name of the tablespace to which the rollback segment belongs.

· State—Status of the rollback segment. The following options are available:

¡ ONLINE—The segment is in online state.

¡ PENDING OFFLINE—The segment is in offline state, but some transactions are still using the rollback segment.

¡ OFFLINE—State that the pending offline segment goes to when the transactions are over.

· Current Size—Size of the rollback segment.

· Current Blocks—Number of current blocks used by the rollback segment.

· Initial Extent Segment—Size of the first extent segment allocated for the rollback segment.

· Next Extent Segment—Size of the second extent segment allocated for the rollback segment.

· Min Extent Segment—Minimum number of extents allocated for the rollback segment.

· Max Extent Segment—Maximum number of extents allocated for the rollback segment.

· Gets—Times of getting rollback segment headers.

· Waits—Waiting times of the rollback segment headers.

· HWM—High-water mark (HWM) of the rollback segment. HWM indicates the position of the last data block in the current segment.

· Shrinks—Shrinking times of the rollback segment.

· Wraps—Wrapping times of the rollback segment.

· Extends—Extending times of the rollback segment.

· Hit Ratio—How often the rollback segment headers have been obtained. Hit Ratio = Gets/(Gets + Waits) × 100%.

Cluster Details

The Cluster Details area displays detailed information for each instance in a cluster. For an Oracle application in standalone mode, this area displays detailed information for only the Oracle application.

The Cluster Details area contains the following fields:

· Instance No.—Number of the instance.

· Instance Name—Name of the instance.

· Host Name—Host name of the instance.

· Version—Version of the instance.

· Startup Time—Time when the instance was started.

· Instance State—State of the instance.

· Database State—State of the cluster database.

· Loading Status—Loading status of the instance.

· REDO Thread Count—Number of Redo threads in the instance.

· Allowing Login—Whether the instance can be logged in to.

· Instance Role—Role of the instance.

· Running Status—Running status of the instance.

Enqueue Request

The Enqueue Request area contains the following fields:

· Total Wait—Number of requests in the queue of the database.

· Total Request—Number of requests of the database.

· Lock Wait Ratio—Ratio of Total Wait to Total Request.

Utilization Statistic

You can click the History Record icon to view the history graph for each field.

The Utilization Statistic area contains the following fields:

· Process Util Rate—Utilization rate of process in the database.

· Session Util Rate—Utilization rate of session in the database.

Traverse Table

The Traverse Table area contains the following field:

Traverse Table Rate—Rate of fully traversed table in the database.

Read By Index

The Read By Index area contains the following field:

Read By INdex Rate—Rate of rows read by index in the database.

Redo Latency

The Redo Latency area contains the following field:

Log Operate Interval—Interval of log writes in the database.

Log Redo

The Log Redo area contains the following field:

QTY Redo Remain—Number of redo logs to be saved in the database.

Jobs

The Jobs area contains the following fields:

· Interuptions—Number of interrupted jobs in the database.

· Failure—Number of failed jobs in the database.

Lock Utilization

The Lock Utilization area contains the following fields:

· Used Locks—Number of locks being used.

· Max. Locks—Maximum number of locks that can be used.

· Lock Utilization Rate—Limited Lock Utilization divided by Limited Lock Utilization.

Transaction Utilization

The Transaction Utilization area contains the following field:

· TX UTIL Rate—Percentage of transaction utilization.

Parallel Query

The Parallel Query area contains the following field:

· Busy Rate—Rate of busy servers when the database executes query parallelly.

User Information

The User Information area contains the following fields:

· ID—ID of the Oracle user.

· Username—Username of the Oracle user.

· Account Status—Account status of the Oracle user.

¡ OPEN—The Oracle user is in normal state.

¡ LOCKED—The Oracle user is in locked state.

¡ EXPIRED—The password of the Oracle user has expired.

¡ LOCKED & EXPIRED—The password of the Oracle user has expired and the Oracle user is in locked state.

· Default Table Space—Name of the default table space.

· Temporary Table Space—Name of the temporary table space.

· Profile—Profile used by the Oracle user. The default is the profile that the Oracle application creates by default.

· Created Time—Time when the Oracle user was created.

· Lock Date—Date when the Oracle user was locked.

· Expiry Date—Date when the Oracle user expired.

· Remaining Lifetime (days)—Number of days before the Oracle user expires. Click the Set Threshold icon to set alarm thresholds for this field.

· DBA YES/NO—Whether the Oracle user is a DBA user.

Backup Information

The Backup Information area contains the following fields:

· Start Time—Start time of the first backup.

· Completion Time—Completion time of the last backup.

· Backup Set Size—Size of the backup set.

· Elapsed Time—Total elapsed time for all backups.

Lowest SCN of the Redo Record in the Log File

The System Change Numbers (SCNs) identify database changes by using numbers in ascending order. The greatest number indicates the latest database change.

The Lowest SCN of the redo record contained in the logfile area contains the following field:

· Lowest SCN of the redo record contained in the logfile—Lowest SCN in the Redo log file at the last polling time.

Fast Recovery Area

The Fast Recovery Area area contains the following fields:

· Fast Recovery Area Path—Fast recovery area path.

· Space Usage—Usage of the fast recovery area space. Click the History Record icon to view the history graph of the space usage.

· Fast Recovery Area Used—Fast recovery area space that has been used. Click the History Record icon to view the history graph of the fast recovery area used.

· Fast Recovery Area Size—Size of the fast recovery area space.

Long Operation Statistics

The Long Operation Statistics area contains the following fields:

· Operation Name—Name of the operation that took a long time.

· Total Workload—Total workload of the operation.

· Unit—Unit for total workload.

· Start Time—Time when the operation started.

SCN Statistics

The SCN Statistics area contains the following fields:

· Name—Name of the object that uses a SCN.

· SCN ID—SCN ID for the object.

· Health Status—Health status of the object.

Long Transaction

The Long Transaction area contains the following fields:

· Start Time—Time when the transaction execution was started.

· Execution Duration—Duration that the transaction has been executed.

· SQL—SQL statements executed by the transaction.

Control File

The Control File area contains the following fields:

· Name—Path and name of the control file.

· Located in Flash Recovery Area—Whether the control file is in the flash recovery area.

· Control File Chunk Size—Size of a single chunk used by the control file.

· Control File Chunk Count—Number of chunks used by the control file.

· Control File Size—Size of the control file, which equals the number of chunks multiplied by the size of a single chunk.

Redo Log File

The Redo Log File area contains the following fields:

· Group Number—Number of the Redo log file group.

· Status—Status of the Redo log file.

· Type—Type of the Redo log file group. Options are ONLINE and STANDBY.

· Member Name—Name of the member log file.

· Located in Flash Recovery Area—Whether the Redo log file is in the flash recovery area.

· First Time—First Redo log time.

Database Lock

The Database Lock area contains the following fields:

· Object Name—Name of the locked object.

· Object Type—Type of the locked object.

· Session ID—ID of the locked session.

· Blocked Session—ID of the session that has been blocked due to the lock.

· Lock Mode—Mode of the lock:

¡ 2—Row-shared lock (Row-S, RS)

¡ 3—Row-exclusive lock (Row-X: RX)

¡ 4—Shared lock (Share, S)

¡ 5—Shared row-exclusive lock (S/Row-X, SRX)

¡ 6—Exclusive lock (Exclusive: X)

· Serial ID—Sequence number of the session.

· Event—Name of the lock event.

· Process ID—ID of the locked process.

· Process No.—Number of the locked process.

· Process Name—Name of the locked process.

· Oracle User—Locked Oracle user.

Object Statistics

The Object Statistics area contains the following fields:

· Owner—Owner of the new object.

· Object Name—Name of the object.

· Object Type—Type of the object, which can be TABLE or INDEX.

· Status—Status of the object, which can be VALID, INVALID, or N/A.

· Creation Time—Time when the object was created.

· Modification Time—Time when the object was last modified.

Invalid Object

The Invalid Object area contains the following fields:

· Owner—Owner of the invalid object.

· Object Name—Name of the object.

· Object Type—Type of the object, which can be TABLE or INDEX.

· Status—Status of the object, which can only be INVALID.

· Creation Time—Time when the object was created.

· Modification Time—Time when the object was last modified.

Index Unavailable

The Index Unavailable area contains the following fields:

· Owner—Owner of the unavailable index.

· Index Name—Name of the index.

· Index Type—Type of the index, which can be NORMAL, BITMAP, FUNCTION-BASED NORMAL, or FUNCTION-BASED BITMAP.

· Status—Status of the object, which can only be UNUSABLE.

· Table Name—Name of the table for the index.

· Deleted—Whether the index has been deleted and is in the recycle bin.

Log File Group

The Log File Group area contains the following fields:

· Group ID—ID of the log file group.

· Group Status—Status of the log file group.

· Group Size—Size of the log file group.

· Archived—Whether the log file group is archived.

· Log File—Path and name of the log file.

Archived Logs

The Archived Logs area contains the following fields:

· Alert Log Path—Path for storing archived logs.

· Archived Log Space Usage—Used archived log space in percentage in the last polling interval. Click the History Record icon to view the history graph of the archived log space usage.

· Archived Log Space Used—Used archived log spaced in bytes in the last polling interval. Click the History Record icon to view the history graph of the archived log space used.

· Archived Log Space Size—Size of the archived log space.

Dispatch Busy

The Dispatch Busy area contains the following fields:

· Dispatch Name—Name of the dispatcher process.

· Dispatch Busy Rate—Busy rate of all dispatchers in the database.

Redo Request

The Redo Request area contains the following fields:

· Wait Class—Class that redo requests belong to.

· Event—Name of the event.

· Average Wait—Average time that redo request waits for.

Details

The Details area contains the following fields:

· Name—Tablespace name.

· Allocated Bytes—Tablespace size.

· Allocated Blocks—Number of data blocks in the tablespace.

· Data Files—Number of data files in the tablespace.

State

The State area contains the following fields:

· Name—Tablespace name.

· State—Tablespace state when APM last polled the Oracle application, which can be ONLINE, OFFLINE, or INVALID.

· Usage Ratio—Usage of the tablespace.

· Free Bytes—Available space that can be used in the tablespace.

· Free Blocks—Number of available data blocks in the tablespace.

· Reads—Times of the tablespace reading data blocks from the disk.

· Writes—Times of the tablespace writing data blocks to the disk.

· Read Time—Tablespace reading time from Oracle application startup to the last polling.

· Write Time—Tablespace writing time from Oracle application startup to the last polling.

· FSFI—Free Space Fragmentation Index value of the tablespace. The smaller the value, the more fragments to be cleared in the tablespace.

Performance Index

The Performance Index area contains the following fields:

· Data File—Name and path of the Oracle application datafile.

· Tablespace—Tablespace where the datafile is located. One datafile locates in only one tablespace.

· State—Datafile state.

· Size—Size of the datafile.

· Reads—Times of reading data from the datafile.

· Writes—Times of writing data to the datafile.

· Average Read Time—Average time of reading data from the datafile.

· Average Write Time—Average time of writing data to the datafile.

Auto Ext

The Auto Ext area contains the following fields:

· Table Name—Name of the database table.

· Auto Ext—Whether the database table can be automatically extended.

· Increment Size—Size that the database table can be automatically extended.

High Used Table

The High Used Table area contains the following fields:

· Space Name—Name of the highly used tablespace.

· Free Rate—Free rate of the tablespace.

Session Statistics

The Session Statistics area contains the following fields:

· Session Count—Number of sessions when APM last polled the Oracle application.

· System Sessions—Number of sessions of the background type.

· User Sessions—Number of sessions of the user type.

· ACTIVE Sessions—Number of sessions in ACTIVE state.

· INACTIVE Sessions—Number of sessions in INACTIVE state.

· KILLED Sessions—Number of sessions in KILLED state.

· CACHED Sessions—Number of sessions in CACHED state.

· SNIPED Sessions—Number of sessions in SNIPED state.

Process Statistics

The Process Statistics area contains the following fields:

· Process Count—Number of processes when APM last polled the Oracle application.

· Background Process—Number of background processes.

Process

The Process area contains the following fields:

· Process Name—Name of the background process.

· Process ID—ID of the background process.

· SPID—Operating system process identifier.

· Serial Number—Process serial number.

· Used Memory—Size of the PGA used by the background process.

· Assigned Memory—Size of the PGA assigned to the background process.

· Freeable Memory—Size of the free PGA for the background process.

· Maximum Memory—Maximum PGA memory ever allocated by the process.

· Status—State of the background process.

· OS User—Operating system process username.

· Terminal—Operating system terminal identifier.

· Program—Program in progress.

· Background—Whether the process is a background process.

Details

The Details area contains the following fields:

· ID—Session ID.

· State—Session state.

· Computer—Name of the computer that established the session with the Oracle application.

· Username—Username used to establish the session with the Oracle application.

· Elapsed Time—Session duration.

· CPU Usage Time—Length of time for which the session has used the CPU.

· Memory Sorts—Number of times that the user performed memory sorting during the session.

· Table Scans—Number of times that the user performed table scan operations during the session.

· Physical Reads—Number of times that the user read from the disk during the session.

· Logical Reads—Number of times that the user read from the memory during the session.

· Submit—Number of times that the user executed commit operations during the session.

· Cursor—Number of cursors that the user used in the session.

· Buffer Hit Ratio—Percentage of number of logical reading times in the buffer pool to total number of logical reading times.

· OS User—Operating system client username.

· Terminal—Operating system terminal name.

· Time Of Logon—Time of logon.

· Command—Command in progress. Specific command names can be queried by the select from * v$sqlcommand statement.

Waiting Sessions

The Waiting Sessions area contains the following fields:

· ID—ID of the waiting session.

· Username—Username used to establish the session with the Oracle application.

· Events—Event that the session was waiting or the last event the session waited.

· Events Occurred—Number of times that the session waited for an event.

· State—State of the waiting session when APM last polled Oracle. The available status includes:

¡ WAITING—The session is waiting.

¡ WAITED UNKNOWN TIME—The time slot for the waiting session is unknown.

· Type—Session type. BACKGROUND and USER indicate that sessions are generated by the background process and user process, respectively.

· Wait Seconds—Length of time for which the session had waited.

Top 10 Wait Events

The Top 10 Wait Events area contains the following fields:

· Event Name—Name of the wait event.

· Wait Count—Number of times that the wait event occurred.

· Wait Duration—Amount of the wait time.

· Average Wait Duration—Amount of the average wait time.

· Wait Duration Ratio—Percentage of the wait time to the DB time. In the case of multiple CPUs, the value for this field can be greater than 100%.

· Wait Type—Type of the wait event.

Top10 SQL by Execution Duration

The Top10 SQL by Execution Duration area displays top 10 SQL statements by accumulated execution duration.

The Top10 SQL by Execution Duration area contains the following fields:

· SQL—SQL statement.

· Cumulative Execution Duration—Total duration used for parsing and executing the SQL statement.

· Cumulative CPU Time—Duration that parsing and executing the SQL statement occupies the CPU.

· Executions—Number of times that the SQL statement is executed.

· Physical Reads—Number of times for physically reading the SQL statement.

· Logical Reads—Number of times for logically reading the SQL statement.

Logical Reads Top10 SQL

The Logical Reads Top10 SQL area contains the following fields:

· SQL—SQL statement.

· Cumulative Execution Duration—Total duration used for parsing and executing the SQL statement.

· Cumulative CPU Time—Duration that parsing and executing the SQL statement has occupied the CPU.

· Executions—Number of times that the SQL statement is executed.

· Physical Reads—Number of times for physically reading the SQL statement.

· Logical Reads—Number of times for logically reading the SQL statement.

Physical Reads Top10 SQL

The Physical Reads Top10 SQL area contains the following fields:

· SQL—SQL statement.

· Cumulative Execution Duration—Total duration used for parsing and executing the SQL statement.

· Cumulative CPU Time—Duration that parsing and executing the SQL statement has occupied the CPU.

· Executions—Number of times that the SQL statement is executed.

· Physical Reads—Number of times for physically reading the SQL statement.

· Logical Reads—Number of times for logically reading the SQL statement.

Session Parameter

The Session Parameter area contains the following fields:

· Name—Name of the parameter.

· Value—Parameter value.

· Is Default—Whether the parameter is set to the default value.

· Is Session Modifiable—Whether the parameter can be changed with ALTER SESSION (TRUE) or not (FALSE).

· Is System Modifiable—Whether the parameter can be changed with ALTER SYSTEM.

¡ IMMEDIATE—The parameter can be changed with ALTER SYSTEM regardless of the type of parameter file used to start the instance. The change takes effect immediately.

¡ DEFERRED—The parameter can be changed with ALTER SYSTEM regardless of the type of parameter file used to start the instance. The change takes effect in subsequent sessions.

¡ FALSE—The parameter cannot be changed with ALTER SYSTEM unless a server parameter file was used to start the instance. The change takes effect in subsequent instances.

· Is Instance Modifiable—For parameters that can be changed with ALTER SYSTEM, whether the value of the parameter can be different for every instance (TRUE) or whether the parameter must have the same value for all Real Application Clusters instances (FALSE).

· Is Modified—Whether the parameter has been modified after instance startup.

¡ MODIFIED—The parameter has been modified with ALTER SESSION.

¡ SYSTEM_MOD—The parameter has been modified with ALTER SYSTEM.

¡ FALSE—The parameter has not been modified after instance startup.

· Description—Description of the parameter.

System Parameter

The System Parameter area contains the following fields: