HCP Tenants Test
Namespaces are owned and managed by administrative entities called tenants. Tenant typically corresponds to an organization, such as division or department within company.
Hitachi Content Platform supports two types of tenants:
- Hitachi Content Platform tenants, which own Hitachi Content Platform namespaces. An Hitachi Content Platform system can have multiple tenants, each of which can own multiple namespaces. You can limit the number of namespaces each tenant can own. In addition to being owned by tenant, each namespace can have an owner that corresponds to an individual Hitachi Content Platform user. The owner of namespace automatically has permission to perform certain operations on that namespace.
- The default tenant, which owns the default namespace and only that namespace. An Hitachi Content Platform system can have only one default tenant.
This test monitors how much physical/logical storage space is occupied by each tenant and alerts the administrators to potential contentions, if any.
Target of the test : Hitachi Content Platform
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each Tenant 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 |
---|---|---|---|
Allocated size |
Indicates the allocated space for this tenant. |
TB |
|
Physical used size |
Indicates the amount of physical space used by this tenant. |
TB |
A low value is desired for these measures.
|
Physical size used |
Indicates the percentage of physical storage space used by this tenant. |
Percent |
|
Logical used size |
Indicates the amount of logical space used by this tenant. |
TB |
A low value is desired for these measures.
|
Logical size used |
Indicates the percentage of logical space used by this tenant. |
Percent |
|
Free size |
Indicates the amount of allocated space unused by this tenant. |
TB |
Ideally, the value of these measures should be high. |
Size free |
Indicates the percentage of allocated space unused by this tenant. |
Percent |