H3C P5730 Monitoring in U-Center 2.0

Configuration Example

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W102-20230922

 

Contents

Introduction· 1

Usage guidelines· 1

Applicable scenarios· 1

Prerequisites· 1

Configuration example· 1

Network configuration· 1

Procedures· 2

Adding an H3C P5730 monitor 2

Configuring the H3C P5730 monitor template· 6

Verifying the configuration· 11

Viewing the H3C P5730 monitor reports· 11

Viewing H3C P5730 threshold alarms· 21

 

Introduction

H3C FlexStorage P5730 is an H3C-proprietary storage device that accommodates various virtual environments.

This document describes the configuration procedure and monitor reports for H3C P5730 monitoring.

Usage guidelines

Applicable scenarios

Use U-Center 2.0 to monitor H3C P5730 in a data center environment.

Prerequisites

·     H3C P5730 is installed and configured successfully, and can correctly start.

·     U-Center 2.0 is installed and deployed successfully.

·     The U-Center 2.0 server can communicate with H3C P5730 correctly.

·     U-Center 2.0 requires users to have access permissions to REST and SSH services when incorporating devices. Please contact the server administrator to obtain the corresponding username, password, and port number.

By default, the H3C P5730 uses ports 8081 and 16022 for REST and SSH services respectively.

 

NOTE: ·     Representational State Transfer (REST) is an application programming interface (API) architecture designed to provide standardized, lightweight, HTTP/HTTPS-based communication for web applications. ·     Secure Shell Protocol (SSH) is an application-layer network security protocol used for encrypted login between servers.

 

Configuration example

Network configuration

As shown in Figure 1, an H3C P5730 in the DC of an enterprise provides storage services for the enterprise. The server administrator wants to use U-Center 2.0 to incorporate and monitor the H3C P5730. Table 1 shows the networking details.

Figure 1 Network diagram

 

Table 1 Networking details

Host name	IP address	Application
Server(U-Center 2.0)	192.167.15.44	U-Center IOM 2.0 (E0711)
Host A	172.50.2.195	H3C FlexStorage P5730

 

Procedures

Adding an H3C P5730 monitor

1.     Log in to U-Center 2.0.

2.     On the top navigation bar, click Monitor.

3.     From the left the navigation pane, select Basic Monitor > Storage.

4.     Click Add and select H3C P5730 from the list to enter the page for adding an H3C P5730 monitor, as shown in Figure 2.

Figure 2 Adding an H3C P5730 monitor

 

5.     Configure basic information, as shown in Table 1.

¡     IP Address: Specify 172.50.2.195 for the H3C P5730.

¡     Name: Use the name automatically generated by U-Center 2.0, which is H3C P5730_172.50.2.195 in this example. You can specify a monitor name as needed.

¡     Description: Enter an application description as needed. No description is specified in this example.

Figure 3 Configuring basic information

 

6.     Configure monitor parameters, as shown in Figure 4.

¡     Add as Monitor Object: This option is enabled by default.

¡     Monitor Template: Use the default Docker template predefined in U-Center 2.0. You can click Settings to select another monitor template or edit the monitor template settings.

For more information about editing monitor template settings, see “Configuring the H3C P5730 monitor template.”

¡     Add as Config Poll Object: By default, a resource object is added as a config poll object. To use the Add as Config Poll Object function, you must purchase the corresponding license for the CMDB product to obtain the quantity-based authorization and functional authorization. Without the license, the page does not display the parameter.

¡     Select Agent: Specify the management station for the monitor. The default agent is Local. In the proxy scenario, you must use proxy to incorporate applications (select Proxy as the agent for the monitor).

Figure 4 Configuring monitor parameters

 

7.     Configure access parameters, as shown in Figure 6.

¡     Monitoring Protocol: Rest General is selected by default. The cluster performance, server performance, and storage volume performance indexes are collected through SSH, so SSH is also selected in this example.

¡     Access Parameter Template Name: Click Settings to select an access parameter template or edit the access parameter template settings.

¡     Username: Username used by the H3C P5730.

¡     Password: Password used by the H3C P5730.

¡     Protocol: Protocol used by the H3C P5730 for login. HTTPS is selected in this example.

¡     Monitor Port: Port used by the H3C P5730 for login. Port 8081 is used in this example.

¡     Connect TimeOut(s): Timeout timer for establishment of the connection between the system and the H3C P5730.

¡     Query TimeOut(s): Timeout timer for data collection from the H3C P5730.

Figure 5 Configuring access parameters 1

 

Figure 6 Configuring access parameters 2

 

8.     Configure resource group settings for the monitored object as needed to facilitate resource management, as shown in Figure 7. This parameter is not specified in this example.

Figure 7 Configuring resource group settings

 

9.     Specify whether or not to enable detection. By default, this feature is enabled, as shown in Figure 8. This example uses the default setting.

Figure 8 Whether or not to enable detection

 

10.     Click Test Connectivity to verify the parameter configuration.

11.     If the connectivity test is passed, click OK.

The added monitor is displayed in the list, as Add Figure 9.

Figure 9 Monitor list

 

Configuring the H3C P5730 monitor template

U-Center 2.0 controls the collection indexes and their thresholds through monitor templates. The system has predefined many monitor templates that can be used directly. You can also modify the monitor templates as needed for custom monitoring.

You can set threshold values for the concerned indexes to monitor the application running status by monitoring the resource alarm status. The following operations are commonly used:

·     Copy a monitor template and edit the threshold settings. For more information, see “Editing threshold settings.”

·     Edit the index collection interval. For more information, see “Editing the index collection interval.”

1.     On the top navigation bar, click Monitor.

2.     From the left navigation pane, select Monitor Options > Monitor Templates to enter the monitor template page, as shown in Figure 10.

Figure 10 Monitor template list

 

3.     In the Select Template Type area, select Storage > H3C > H3C P5730 to view the H3C P5730 monitor template, as shown in Figure 11. You can perform the following operations in the Actions column:

¡     Click the Edit icon  to enter the page for editing the monitor template.

¡     Click the Copy template icon  to enter the page for copying the monitor template. For example, if you copy monitor template A, the system generates monitor template A_copy. You can edit and save the new template on the page for copying the template.

¡     Click the Edit Threshold icon  to access the Threshold Settings tab of the monitor template modification page.

Figure 11 H3C P5730 monitor template

 

4.     Click the Edit icon  in the Actions column of the monitor template to enter the page for editing the monitor template, as shown in Figure 12.

Figure 12 Editing the monitor template

 

Editing threshold settings

As a best practice, do not edit the indexes in the predefined monitor templates of the system. As a best practice to edit multiple parameters, first copy the monitor template, edit the parameters in the copied template, and then apply the edited monitor template to the application.

This example modifies index Bytes Written in index group Volume.

1.     Click the Copy Template icon  to enter the page for copying the monitor template.

2.     On the Index Settings tab, expand the Volume index group, as shown in Figure 13.

Figure 13 Volume index group

 

3.     Click the Threshold icon  in the Actions column for index Bytes Written. On the page that opens, configure the parameters as shown in Figure 14.

¡     Threshold Type: U-Center 2.0 supports multiple threshold types, including Common Threshold, Composite Threshold, Index-Based Rule, and Instance Loss Threshold. Different types require different configurations. Select a threshold type as needed, set a comparison operator, and select a threshold level. The threshold types of some indexes have been predefined in U-Center 2.0, and cannot be edited.

¡     Applicable Time: You can select all time or customize a time range. Custom Time: Any time range from Monday to Sunday. In this example, select All Time.

¡     Threshold Settings: For index Bytes Written, select Notification in this example, and set the threshold and the maximum number of consecutive occurrences. In this example, select Greater Than. When the written bytes exceed the set threshold value and the number of consecutive occurrences is reached, a notification alarm will be generated.

Figure 14 Editing threshold settings

 

4.     Click OK to save the edited parameters.

5.     Click the Threshold Settings tab to view the configuration, as shown in Figure 15.

Figure 15 Edited threshold settings

 

6.     If you do not need to edit other parameters in the monitor template, click OK at the bottom of the page to save the configuration.

The copied monitor template is created successfully, as shown in Figure 16.

Figure 16 Added monitor template

 

7.     From the left the navigation pane, select Basic Monitor > Storage, as shown in Figure 17.

Figure 17 Storage

 

8.     Replace the monitor template and save it. The system will use the new monitor template at the next collection interval.

You can change the monitoring template for a resource by using the following methods:

¡     To replace the monitor template for a resource, click the Edit icon  in the Actions column on the storage page. On the page that opens, click Settings to the right of Monitor Template, as shown in Figure 18. On the window that opens, select the target monitor template.

¡     To replace the monitor template for multiple resources of the same type, select resources of the same type on the storage page, click More, and then click Change Monitor Template. On the page that opens, replace the monitor template for the resources in bulk.

Figure 18 Editing the monitor template

 

Editing the index collection interval

U-Center 2.0 controls the interval for collecting indexes through monitor templates. You can specify different collection intervals for different index groups.

1.     On the top navigation bar, click Monitor.

2.     From the left navigation pane, select Monitor Options > Monitor Templates to enter the monitor template page.

3.     In the Select Template Type area, select Storage > H3C > H3C P5730, as shown in Figure 19.

Figure 19 Monitor templates page

 

4.     Click the Edit icon  in the Actions column of H3C P5730_copy to enter the page for editing the monitor template, as shown in Figure 20.

The list displays monitor indexes for the monitor template. This example takes the collection interval configuration of the Volume index group for illustration.

Figure 20 Editing the monitor template

 

5.     Select the Volume index group, and click Edit Collection Interval. On the page that opens, edit the collection interval, as shown in Figure 21.

Figure 21 Editing the collection interval

 

6.     Select a collection interval from the Collection Interval list, which is 4 minutes in this example.

7.     Click OK. The edited collection interval is as shown in Figure 22.

Figure 22 Edited collection interval

 

8.     Click OK on the page for editing the monitor template. The edited monitor template automatically takes effect at the next collection interval.

Verifying the configuration

Viewing the H3C P5730 monitor reports

 

NOTE: ·     If the value of an index exceeds the corresponding threshold, the background color of the value in the monitor report changes to the color for alarms of the corresponding level defined in U-Center 2.0. ·     If an application has triggered alarms of different levels, the alarm state field displays the highest level alarm that has been triggered.

 

1.     On the top navigation bar, click Monitor.

2.     From the left the navigation pane, select Basic Monitor > Storage. Verify that the alarm state has changed after a period of collection, as shown in Figure 23.

Figure 23 Monitor list

 

3.     Click the H3C P5730_172.50.2.195 link and view the monitor report on the page that opens, as shown in Figure 24.

Figure 24 Part of an H3C P5730 monitor report

 

This section describes the fields in each area of the monitor report by using the monitor indexes of the default H3C P5730 monitor template.

Availability Today

Figure 25 Availability Today area layout

 

·     Pie Chart: Percentage of availability status for the storage device in the current day. You can view the corresponding percentage data for each pie slice by hovering over it with the mouse.

·     Current Availability: Availability of the current application.

¡     Available: The monitored object can be correctly connected and the monitor data can be collected.

¡     Inaccessible: The monitored object cannot be reached, and an associated alarm will be generated.

¡     Unavailable: The monitored object cannot be connected, and an associated alarm will be generated.

¡     Collect Disabled: The monitored object is not monitored, and its health status is unknown.

·     Duration

¡     Available Time: Total accumulated time that the application has been running normally since 00:00 today.

¡     Inaccessible Time: Total accumulated time that the application has been inaccessible since 00:00 today.

¡     Unavailable Time: Total accumulated duration of protocol connection failures for the application since 00:00 today.

¡     Collect Disabled Time: Total accumulated duration of collection stoppage for the application since the user manually disabled monitoring and collection for the device.

 

NOTE: For a newly added application monitor, the system starts collecting statistics for the Available, Unavailable, and Collect Disabled fields since the monitor is successfully added on the current day. The availability status data with duration of 0 are not displayed.

 

·     Weekly History: To view the availability of the application in the past 7 days, click Weekly History. The system calculates the availability of an application for the past 7 days by hour. To view the time duration percentages of availability states at a specific time point, hover the cursor over that time, as shown in Figure 26.

Figure 26 Weekly history

 

·     Weekly History: To view the availability of the application in the past 30 days, click Weekly History. The system calculates the availability of an application for the past 30 days by Daily. The monthly availability data is collected in days. To view the time duration percentages of availability states at a specific time point, hover the cursor over that time point, as shown in Figure 27.

Figure 27 Monthly history

 

CPU usage ratio

Figure 28 CPU Usage Ratio area layout

 

·     CPU Usage Ratio: CPU usage of the H3C P5730.

Memory usage ratio

Figure 29 Memory Usage ratio area layout

 

·     Memory Usage Ratio: Memory usage of the H3C P5730.

Cluster

Figure 30 Cluster area layout

 

·     Name: Cluster name.

·     Module Count: Number of storage modules in the cluster.

·     Storage Module IP: IP address of each storage module in the cluster.

·     Virtual IP Enabled: Whether the virtual IP address is available.

·     Available Space: Available space in the current cluster.

·     Total Space: Total space of the cluster.

·     Supported Features: Features supported by the cluster.

·     Adaptive Optimization Supported: Whether the cluster supports adaptive optimization.

·     ID: Cluster ID.

·     Description: Description of the cluster.

Cluster performance

Figure 31 Cluster Performance area layout

 

·     Cluster Performance Unit: Name of the cluster.

·     I/O Reads: Number of read operations per second in the cluster.

·     I/O Writes: Number of write operations per second in the cluster.

·     I/O Total: Total number of read and write operations per second in the cluster.

·     I/O Read Rate: Number of bytes read per second in the cluster.

·     I/O Write Rate: Number of bytes written per second in the cluster.

·     I/O Transfer Rate: Number of bytes read and written per second in the cluster.

·     Read Queue Depth: Read queue depth in the cluster.

·     Write Queue Depth: Write queue depth in the cluster.

·     Total Queue Depth: Total queue depth in the cluster.

·     Read Latency: Latency of read operations in the cluster.

·     Write Latency: Latency of write operations in the cluster.

Cluster virtual IP

Figure 32 Cluster Virtual IP area layout

 

·     Name: Cluster name.

·     ID: Cluster ID.

·     Cluster Virtual IP ID: ID of the cluster virtual IP.

·     IP: Virtual IP of the cluster in IPv4 format.

·     Mask: IPv4 subnet mask.

Cluster space

Figure 33 Cluster Space area layout

 

·     Name: Cluster name.

·     ID: Cluster ID.

·     Cluster Space ID: ID of the cluster space.

·     Replication Level: Replication level of the cluster.

·     Available Space: Available space for each level.

Volume

Figure 34 Volume area layout

 

·     ID: Volume ID.

·     ClusterId: Cluster ID of the storage volume.

·     Name: Name of the storage volume.

·     SerialNumber: Serial number of the storage volume.

·     Description: Description of the storage volume.

·     Created At: Time when the storage volume was created.

·     Alternate Name: Alternate name of the storage volume.

·     Size: Capacity of the storage volume.

·     Provisioned Space: Provisioned space for the storage volume.

·     Replica Count: Number of data copies stored in the storage system.

·     iSCSI Qualified Name: iSCSI IQN.

·     Bytes Written: Written space of the storage volume.

·     Availability: Whether the volume is online or offline.

·     Cluster: Cluster to which the storage volume belongs.

·     Transport Server ID: ID of the server to which the storage volume belongs on the transport server.

·     Data Protection Level: Data protection level of the storage volume.

¡     0: Network RAID0 (None)

¡     1: Network RAID5 (Single Parity)

¡     2: Network RAID10 (2-Way Mirror)

¡     3: Network RAID10 (3-Way Mirror)

¡     4: Network RAID10 (4-Way Mirror)

¡     5: Network RAID6 (Dual Parity)

·     Transport Type: Transport method of the storage volume.

¡     0: iSCSI.

¡     1: Fiber channel.

·     Primary Volume: Whether the storage volume is the primary storage volume.

Volume performance

Figure 35 Volume Performance area layout

 

·     Volume Performance Unit: Name of the storage volume.

·     I/O Reads: Number of read operations per second in the storage volume.

·     I/O Writes: Number of write operations per second in the storage volume.

·     I/O Total: Total number of read and write operations per second in the storage volume.

·     I/O Read Rate: Number of bytes read per second in the storage volume.

·     I/O Write Rate: Number of bytes written per second in the cluster.

·     I/O Transfer Rate: Number of bytes read and written per second in the storage volume.

·     Read Queue Depth: Read queue depth in the storage volume.

·     Write Queue Depth: Write queue depth in the storage volume.

·     Total Queue Depth Total queue depth in the storage volume.

·     Read Latency: Latency of read operations in the storage volume.

·     Write Latency: Latency of write operations in the storage volume.

Volume status

Figure 36 Volume Status area layout

 

·     Name: Name of the storage volume.

·     Thinly Provisioned: Whether the storage volume is thinly provisioned.

·     In Deletion: Whether the storage volume has been deleted.

·     VIP Rebalancing: Enabling status of the VIP rebalancing feature.

·     Enabled for Adaptive Optimization: Enabling status of the adaptive optimization feature.

·     In Migration: Whether data of the storage volume is in migration.

·     SCSI LUN Status: SCSI LUN status of the storage volume.

·     Unrecoverable I/O Errors: Whether the storage volume has unrecoverable I/O errors.

·     Restripe Pending Status: Restripe pending status of the storage volume.

Volume iSCSI session

Figure 37 Volume iSCSI Session area layout

 

·     Volume: Name of the storage volume.

·     Session id: iSCSI session identifier.

·     Identifier: ID for the iSCSI initiator.

·     Server: Name of the iSCSI server.

·     Gateway IP: Host IP address of the gateway.

·     Initiator IP: IP address of the iSCSI initiator.

·     Initiator Port: Port number of the iSCSI initiator.

·     IQN: IQN of the iSCSI initiator.

·     Session ID: iSCSI session ID.

·     Session Resetting: Whether the iSCSI session is reset.

·     Status: Status of iSCSI connection.

·     Target IP: IP address of the iSCSI target.

·     Target Port: Port number of the iSCSI target.

·     Target Portal Group Tag: Tag of the iSCSI target portal group.

Volume ACL

Figure 38 Volume ACL area layout

 

·     ID: Volume ID.

·     ACL ID: ACL ID of the storage volume, which is used to identify and authorize users or groups.

·     Volume Performance Unit: Name of the storage volume.

·     Server: Server name.

·     Exclusive Access Right: Whether only one process or user has the permission to access certain resources.

·     Read Access Right: Permission to read certain resources.

·     Write Access Right: Permission to write to certain resources.

·     LUN: LUN assigned to the storage volume for these permissions. It is applicable only to fibre channel connections. It is used to identify hard drives or disk arrays, and represents specific virtual disks in storage technologies such as SCSI, iSCSI, and FC.

Snapshot

Figure 39 Snapshot area layout

 

·     ID: Snapshot ID.

·     Name: Snapshot name.

·     SerialNumber: Serial number of the storage volume.

·     Description: Description of the snapshot.

·     Created At: Time when the snapshot was created.

·     Alternate Name: Alternate name of the snapshot.

·     Transport Type: SCSI transport type for the snapshot.

·     Size: Size of the snapshot.

·     Provisioned Space: Provisioned space for the snapshot.

·     iSCSI Qualified Name: iSCSI IQN.

·     Primary Snapshot: Whether the snapshot is a primary snapshot (as opposed to a remote snapshot).

·     Bytes Written: Written space of the snapshot.

·     Availability: Whether the snapshot is online or offline.

·     Cluster: Name of the cluster to which the snapshot belongs.

·     Cluster ID: ID of the cluster to which the snapshot belongs.

·     Used Writable Space: Amount of data written to the snapshot.

·     Management Identifier: Identifier of the application managing the snapshot.

·     Transport Server ID: ID of the transport server. It is applicable only to fibre channels.

Snapshot status

Figure 40 Snapshot Status area layout

 

·     Name: Snapshot name.

·     In Deletion: Whether the snapshot has been deleted.

·     Thinly Provisioned: Whether the snapshot is thinly provisioned. This provisioning mode reduces the space occupied by the snapshot.

·     Scheduled Generation: Whether the snapshot was created as scheduled.

·     In Migration: Whether the snapshot is in migration.

·     SCSI LUN Status: Status of the SCSI LUN.

·     Unrecoverable I/O Errors: Whether the snapshot has unrecoverable I/O errors.

·     Restripe Pending Status: Restripe pending status of the snapshot.

·     Replication Status: Replication status of the snapshot.

·     Resynchronization Status: Resynchronization status of the snapshot.

·     Migration Status: Migration status of the snapshot.

·     Licensed: Whether the snapshot is licensed.

·     Fibre Channel Transport Status: Fibre channel transport status.

Snapshot iSCSI session

Figure 41 Snapshot iSCSI session.

 

·     ID: Snapshot ID.

·     Snapshot Session ID: Session ID of the snapshot.

·     Snapshot: Snapshot name.

·     Server: Server name.

·     Gateway IP: Host IP address of the gateway.

·     Initiator IP: IP address of the iSCSI initiator.

·     Initiator Port: Port number of the iSCSI initiator.

·     IQN: IQN of the iSCSI initiator.

·     Session ID: iSCSI session ID.

·     Session Resetting: Whether the session is being reset.

·     Status: Status of iSCSI connection.

·     Target IP: IP address of the iSCSI target.

·     Target Port: Port number of the iSCSI target.

·     Target Portal Group Tag: Tag of the iSCSI target portal group.

Snapshot ACL

Figure 42 Snapshot ACL

 

·     ID: Snapshot ID.

·     ACL ID: ACL ID of the snapshot.

·     Snapshot: Snapshot name.

·     Server: Server name.

·     Exclusive Access Right: Exclusive access right.

·     Read Access Right: Read access right.

·     Write Access Right: Write access right.

·     LUN: LUN assigned to the snapshot for these permissions. It is applicable only to fibre channels.

Server

Figure 43 Server area layout

 

·     ID: Server ID.

·     Name: Server name.

·     Description: Description of the server.

·     Boot Volume ID: Fiber channel boot volume identifier for the server.

·     Boot Volume LUN: Fibre channel boot volume LUN for the server.

·     CHAP Authentication: Whether CHAP is required for the server.

·     CHAP Initiator Secret: CHAP initiator secret for the server.

·     CHAP Name: Name of the CHAP.

·     CHAP Target Secret: CHAP target secret.

·     Controlling Server Name: Name or IP address of the controlling server.

·     Fibre Channel Available: Availability of the fibre channel.

·     In Server Cluster: Whether the server belongs to a cluster.

·     iSCSI Enabled: Enabling status of iSCSI.

·     iSCSI Qualified Name: iSCSI IQN.

·     iSCSI LoadBalancing Enabled: Enabling status of iSCSI load balancing.

Viewing H3C P5730 threshold alarms

1.     In the resource details window, the Dashboard tab displays the name, type, health status, and suspension state of the monitored application. If an application has triggered alarms of different levels, the Health Status field displays the highest level of alarms triggered.

Based on the configuration in this example, H3C P5730 will generate alarms of the Notification level and display this alarm level for the health status, as shown in Figure 44.

Figure 44 Monitor overview

 

2.     Click the health status information link or click the Alarm Information tab to enter the alarm information page, as shown in Figure 45.

Figure 45 Alarm information

 

3.     Click the alarm information link to view the alarm details, as shown in Figure 46.

Figure 46 Alarm details

 

4.     Verify that the alarm information is correct, and then click the Unacked link, as shown in Figure 47.

Figure 47 Acknowledging the alarm

 

5.     Resolve issues that trigger the alarm or adjust the alarm threshold, and then click Active in the Clearing State column to clear the alarm, as shown in Figure 48.

Figure 48 Clearing the alarm

 

U-Center 2.0 periodically monitors applications. If the collected index values do not meet the threshold conditions in the next collection interval, the alarm status will be automatically restored and new index values will be recorded.

After all alarms are cleared, the health status of the application will also be restored to normal, as shown in Figure 49.

Figure 49 Alarm status recovered