The hardware listed below is required when using this software.
No. | Operation server | Supported model |
|---|---|---|
1 | Administrative server | Over 512MB memory and CPU is Pentium(R)III 1.2GHz or better |
2 | PRIMEQUEST | |
3 | PRIMERGY |
The basic software listed below is required when using this software.
No. | Product name | Remarks |
|---|---|---|
1 | Red Hat Enterprise Linux 5 (for x86) | Modified kernel is required. Obtain a modified kernel and create a modified kernel update CD. Essential software such as driver kit and update kit also need to be prepared, if any. Refer to server instruction manuals or Linux installation guide for essential software information. In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly. |
2 | Red Hat Enterprise Linux 5 (for Intel64) | |
3 | Red Hat Enterprise Linux 5 (for Intel Itanium) | Operation server is only PRIMEQUEST. In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly. |
4 | Red Hat Enterprise Linux 5.1 (for x86) | Modified kernel is required. Obtain a modified kernel and create a modified kernel update CD. Essential software such as driver kit and update kit also need to be prepared, if any. Refer to server instruction manuals or Linux installation guide for essential software information. In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly. |
5 | Red Hat Enterprise Linux 5.1 (for Intel64) | |
6 | Red Hat Enterprise Linux 5.1 (for Intel Itanium) | Operation server is only PRIMEQUEST. In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly. |
7 | Red Hat Enterprise Linux 5.2 (for x86) | Modified kernel is required. Obtain a modified kernel and create a modified kernel update CD. Essential software such as driver kit and update kit also need to be prepared, if any. Refer to server instruction manuals or Linux installation guide for essential software information. In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly. |
8 | Red Hat Enterprise Linux 5.2 (for Intel64) | |
9 | Red Hat Enterprise Linux 5.2 (for Intel Itanium) | Operation server is only PRIMEQUEST. In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly. |
10 | Red Hat Enterprise Linux 5.3 (for x86) | Modified kernel is required. Obtain a modified kernel and create a modified kernel update CD. Essential software such as driver kit and update kit also need to be prepared, if any. Refer to server instruction manuals or Linux installation guide for essential software information. In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly. |
11 | Red Hat Enterprise Linux 5.3 (for Intel64) | |
12 | Red Hat Enterprise Linux 5.4 (for x86) | |
13 | Red Hat Enterprise Linux 5.4 (for Intel64) |
The required software listed below is required when using this software.
No. | Product name | Version / Level | Remarks |
|---|---|---|---|
1 | PRIMECLUSTER Enterprise Edition | 4.2A30 or later | Either one of the two software is required when a cluster is configured by the Admin Server. |
2 | PRIMECLUSTER HA Server | 4.2A30 or later |
There is no Exclusive software.
The required batches listed below are required when using this software.
No. | Product name | Batch ID | Remarks |
|---|---|---|---|
1 | Red Hat Enterprise Linux 5 (for x86) | None | - |
2 | Red Hat Enterprise Linux 5 (for Intel64) | None | - |
3 | Red Hat Enterprise Linux 5 (for Intel Itanium) | None | - |
4 | Red Hat Enterprise Linux 5.1 (for x86) | None | - |
5 | Red Hat Enterprise Linux 5.1 (for Intel64) | None | - |
6 | Red Hat Enterprise Linux 5.1 (for Intel Itanium) | None | - |
7 | Red Hat Enterprise Linux 5.2 (for x86) | None | - |
8 | Red Hat Enterprise Linux 5.2 (for Intel64) | None | - |
9 | Red Hat Enterprise Linux 5.2 (for Intel Itanium) | None | - |
10 | Red Hat Enterprise Linux 5.3 (for x86) | None | - |
11 | Red Hat Enterprise Linux 5.3 (for Intel64) | None | - |
12 | Red Hat Enterprise Linux 5.4 (for x86) | None | - |
13 | Red Hat Enterprise Linux 5.4 (for Intel64) | None | - |
For new installations, the following static disk space is required.
No. | Decretory | Required disk space | Remarks |
|---|---|---|---|
1 | /etc | 1 | - |
2 | /var | 2 | - |
3 | /opt | 300 | - |
4 | /usr | 1 | - |
The required dynamic disk space is as below.
The following disk space is required for each directory, in addition to the static disk resources.
No. | Directory | Required disk space | Remarks |
|---|---|---|---|
1 | /etc | 5 + 1(*A) + 1.2(*B) | *A : Environment definition file Calculated the space required for databases assuming 100 products |
2 | /var | 1055 + (*E) + 30(*C) + 20(*D) | *C : Log Calculated the space required for databases assuming 1000 servers and two devices for each (12KB * Number of registered servers + 4KB * Number of registered devices) |
Repository for Manager
For Manager, the following amount of memory is required, depending on the numbers of managed storage modes, switches, and storage units.
Amount of disk space (MB) = 1 + [Number of target units] * 4
Additionally, when performance management is being performed, based on the fibre channel switch used to collect the performance information, the type of target (the ETERNUS/GR series), the number of logical units involved, the number of DE (Disk Enclosure), and the number of days for which information is to be collected, the required capacity given below becomes necessary.
Information
The default number of days for collection is seven. The number of secured LUs (Logical Units) is the actual number of LUs the functions of which are secured in order to perform performance management for the ETERNUS/GR series. Performance management is secured in units of 64 LUN for the ETERNUS/GR series. Therefore, when instructed to secure from LUN 15 to 200, the information for the actual LUs 0 to 255 (256 in total) would be secured.
Device | Required disk space |
|---|---|
ETERNUS8000 models 700, 900, 1100 and 2100 | The firmware version is previous V11L40: The firmware version is V11L40 or later: [*1] The "number of secured RAIDGroups" is the number of RAIDGroups created from the secured LUs. When monitoring the performance for the number of active disks: |
ETERNUS DX8400/DX8700 | (Number of days to collect + 1) * (24090 + (60 + 0.2 * number of DEs + 0.2 * number of secured LUs + 0.3 * number of secured RAIDGroups[*1]) * (86400 / performance monitoring interval (seconds)) + (79 * number of DEs) + (89 * number of secured LUs) + (103 * number of secured RAIDGroups[*1])) / 1024 [*1] The "number of secured RAIDGroups" is the number of RAIDGroups created from the secured LUs. When monitoring the performance for the number of active disks: |
ETERNUS6000 | (Number of days to collect + 1) * (9.85 + (0.06 + 13.43 / performance monitoring interval (seconds)) * number of secured LUs[*1] + 1956.45 / performance monitoring interval (seconds)) [*1] For ETERNUS6000, it is counted as a total number of LUs (Logical Unit) targeted for performance monitoring. |
ETERNUS4000 models 300 and 500 | The firmware version is previous V11L40: The firmware version is V11L40 or later: [*1] The "number of secured RAIDGroups" is the number of RAIDGroups created from the secured LUs. When monitoring the performance for the number of active disks: |
ETERNUS DX400 series | (Number of days to collect + 1) * (6837 + (17 + 0.2 * number of DEs + 0.2 * number of secured LUs + 0.3 * number of secured RAIDGroups[*1]) * (86400 / performance monitoring interval (seconds)) + (79 * number of DEs) + (89 * number of secured LUs) + (103 * number of secured RAIDGroups[*1])) / 1024 [*1] The "number of secured RAIDGroups" is the number of RAIDGroups created from the secured LUs. When monitoring the performance for the number of active disks: |
ETERNUS3000 (except models 80 and 100) | (Number of days to collect + 1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 253.13 / Performance monitoring interval (seconds) + 1.29) |
ETERNUS3000 models 80 and 100 | (Number of days to collect + 1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + (38.73 / performance monitoring interval (seconds)) + 1.29) |
ETERNUS2000 | (Number of days to collect +1) * (140 + (0.7 + 0.2 * number of installed DEs + 0.3 * (number of secured LUs + number of secured RAIDGroups[*1])) * (86400 / performance monitoring interval (seconds)) + (60 * number of installed DEs) + (50 * (number of secured LUs + number of secured RAIDGroups[*1]))) / 1024 [*1] The "number of secured RAIDGroups" is the number of RAIDGroups created from the secured Lus. When monitoring the performance for the number of active disks: |
ETERNUS DX60/DX80/DX90 | (Number of days to collect + 1) * (240 + (1.2 + 0.3 * number of DEs + 0.3 * (number of secured LUs + number of secured RAIDGroups[*1])) * (86400 / performance monitoring interval (seconds)) + (95 * number of DEs) + (50 * (number of secured LUs + number of secured RAIDGroups[*1]))) / 1024 [*1] The "number of secured RAIDGroups" is the number of RAIDGroups created from the secured Lus. When monitoring the performance for the number of active disks, power consumption, and temperature: |
ETERNUS GR740/GR820/GR840 | (Number of days to collect + 1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 341.95 / performance monitoring interval (seconds) + 1.67) |
ETERNUS GR720/GR730 | (Number of days to collect + 1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + 138.43 / performance monitoring interval (seconds) + 0.65) |
ETERNUS SN200 series Fibre Channel switch PRIMERGY Fibre Channel Switch Blade PRIMERGY Fibre Channel Switch Blade(4Gbps) Brocade Fibre Channel Switch | (Number of days to collect +1) * (30 / performance monitoring interval (seconds)) * 1.6 |
ETERNUS SN200 series Fibre Channel switch Brocade Fibre Channel Switch | (Number of days to collect +1) * (30 / performance monitoring interval (seconds)) * 3.2 |
ETERNUS SN200 series Fibre Channel switch Brocade Fibre Channel Switch | (Number of days to collect +1) * (30 / performance monitoring interval (seconds)) * 13 |
ETERNUS SN200 series Fibre Channel switch Brocade Fibre Channel Switch | (Number of days to collect +1) * (30 / performance monitoring interval (seconds)) * 26 |
ETERNUS SN200 series Fibre Channel switch Brocade Fibre Channel Switch | (Number of days to collect +1) * (30 / performance monitoring interval (seconds)) * 39 |
ETERNUS SN200 MDS series Fibre Channel switch | (Number of days to collect +1) * 0.1 * maximum number of slots supported by device[*1] * 128 * (30 / performance monitoring interval (seconds)) [*1] Use 1 as the maximum number of slots for MDS9120 |
Example
When securing the performance information of 512LUs on an ETERNUS3000 model 200, at 30 second intervals for 7 days,
8 * (30 / 30) * 375 * 512 / 1024 = 1500MB is required.
Additionally, when performance information is output using the performance information operation command, the following disk space is required, depending on the number of LUs of the ETERNUS series and Fibre Channel switches, number of DEs, number of ports that is used to collect performance information, and number of days of performance information output.
Each element (number of installed CM CPUs, number of installed DEs, installed CA Ports, installed CM Ports, LUs, RAIDGroups, and installed FC Ports) is the number mounted in the device when the command is executed.
Device | Required disk space |
|---|---|
ETERNUS4000 models 300 and 500 | Number of days to output * (((0.3 + 0.4 * number of installed DEs + 0.1 * number of installed CA Ports + 0.2 * (number of LUs + number of RAIDGroups)) * (86400 / performance monitoring interval (seconds))) + (0.9 + 0.8 * number of installed DEs + 0.2 * number of installed CA Ports + 0.4 * (number of LUs + number of RAIDGroups) ) ) / 1024 |
ETERNUS DX400 series | Number of days to output * (((0.1 + 0.2 * number of installed DEs + 0.1 * number of installed CA Ports + 0.2 * (number of LUs + number of RAIDGroups) + 0.1 * number of installed CM CPUs) * (86400 / performance monitoring interval (seconds))) + (0.9 + 0.8 * number of installed DEs + 0.2 * number of installed CA Ports + 0.4 * (number of LUs + number of RAIDGroups) + 0.1 * number of installed CM CPUs) ) / 1024 |
ETERNUS2000 | Number of days to output * (((0.1 + 0.2 * number of installed DEs + 0.1 * number of installed CM Ports + 0.2 * (number of LUs + number of RAIDGroups)) * (86400 / performance monitoring interval (seconds))) + (0.2 + 0.3 * number of installed DEs + 0.2 * number of installed CM Ports + 0.4 * (number of LUs + number of RAIDGroups) ) ) / 1024 |
ETERNUS DX60/DX80/DX90 | Number of days to output * (((0.1 + 0.4 * number of installed DEs + 0.1 * number of installed CM Ports + 0.2 * (number of LUs + number of RAIDGroups)) * (86400 / performance monitoring interval (seconds))) + (0.2 + 0.6 * number of installed DEs + 0.2 * number of installed CM Ports + 0.4 * (number of LUs + number of RAIDGroups) ) ) / 1024 |
Fibre Channel Switch | Number of days to output * (0.1 + number of installed FC ports + (0.1 * number of installed FC ports)) + (0.1 + number of installed ports + (0.1 * number of installed FC ports * (86400 / performance monitoring interval (seconds))) / 1024 |
See
For the command, refer to "12.2.1.6 Performance information operation command (storageadm perfdata)" in the ETERNUS SF Storage Cruiser User's Guide.
The minimum memory required for operation of this software is indicated.
No. | Required memory (Unit : MB) | Remarks |
|---|---|---|
1 | 200 | - |
The minimum swap required for operation of this software is indicated.
No. | Swap volume (Unit: MB) | Remarks |
|---|---|---|
1 | 300 | - |
