HCP Services Test
Hitachi Content Platform services are responsible for optimizing the use of system resources and maintaining the integrity and availability of the stored data. Each of the nine services as listed below performs specific function that contributes to the overall health and viability of the system.
- Capacity Balancing: This service attempts to keep the usable storage capacity balanced (roughly equivalent) across all storage nodes in the system.
- Compression: This service compresses object data to make more efficient use of physical storage space.
- Content verification: It guarantees data integrity of repository objects and detects and repairs metadata discrepancies, if any.
- Disposition: This service is an automatic cleanup of expired objects. A namespace configuration policy authorizes Hitachi Content Platform to automatically delete objects after their retention period expires.
- Duplicate elimination: Identifies and eliminates redundant objects in the repository, and merges duplicate data to free space.
- Garbage Collection: This service retrieves storage space by purging hidden data and metadata for objects marked for deletion or left behind by incomplete transactions.
- Protection: It enforces data protection level policy compliance to ensure the proper number of copies of each object exists in the system.
- Scavenging: This service ensures that all objects in the repository have valid metadata, and reconstructs metadata in case the metadata is lost or corrupted.
- Storage Tiering: It determines which storage tiering strategy applies to an object; evaluates where the copies of the object should reside based on the rules in the applied service plan.
This test monitors the status of each service and alerts the administrators if any service switches to an abnormal state.
Target of the test : Hitachi Content Platform
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each HCP Service of the target Hitachi Content Platform.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The IP address of the target switch that is being monitored. |
|
SNMPPort |
The port at which the monitored target exposes its SNMP MIB; the default is 161. |
|
SNMPVersion |
By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list. |
|
SNMPCommunity |
The SNMP community name that the test uses to communicate with the switch. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVersion chosen is v3, then this parameter will not appear. |
|
Username |
This parameter appears only when v3 is selected as the SNMPVersion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter. |
|
AuthPass |
Specify the password that corresponds to the above-mentioned Username. This parameter once again appears only if the SNMPversion selected is v3. |
|
Confirm Password |
Confirm the AuthPass by retyping it here. |
|
AuthType |
This parameter too appears only if v3 is selected as the SNMPversion. From the AuthType list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:
|
|
EncryptFlag |
This flag appears only when v3 is selected as the SNMPVersion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. |
|
EncryptType |
If the EncryptFlag is set to Yes, then you will have to mention the encryption type by selecting an option from the EncryptType list. SNMP v3 supports the following encryption types:
|
|
EncryptPassword |
Specify the encryption password here. |
|
Confirm Password |
Confirm the encryption password by retyping it here. |
|
Timeout |
Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 10 seconds. |
|
Data Over TCP |
By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic – for instance, certain types of data traffic or traffic pertaining to specific components – to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No. |
|
EngineID |
This parameter appears only when v3 is selected as the SNMPVersion. Sometimes, the test may not report metrics when AES192 or AES256 is chosen as the Encryption type. To ensure that the test report metrics consistently, administrators need to set this flag to Yes. By default, this parameter is set to No. |
| Measurement | Description | Measurement Unit | Interpretation | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Service status |
Indicates the current status of this service. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the current status of this service. |
